Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: milvus pulsar error too many requests to the same bookie #33171

Open
1 task done
JamesBonddu opened this issue May 20, 2024 · 2 comments
Open
1 task done

[Bug]: milvus pulsar error too many requests to the same bookie #33171

JamesBonddu opened this issue May 20, 2024 · 2 comments
Assignees
Labels
kind/bug Issues or changes related a bug triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@JamesBonddu
Copy link

JamesBonddu commented May 20, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.4.1
- Deployment mode(standalone or cluster): cluster
- MQ type(rocksmq, pulsar or kafka): pulsar
- SDK version(e.g. pymilvus v2.0.0rc2): pymilvus 2.4
- OS(Ubuntu or CentOS): Ubuntu
- CPU/Memory: 512/1T
- GPU: 3090 * 8
- Others:

Current Behavior

milvus plusar error too many requests to the same bookie
plusar 2.8.2

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

milvus-204-05-20.zip

Anything else?

maybe we can upgrade pulsar after 2020-1

apache/pulsar#6163

No response

@JamesBonddu JamesBonddu added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 20, 2024
@JamesBonddu JamesBonddu changed the title [Bug]: milvus plusar error too many requests to the same bookie [Bug]: milvus pulsar error too many requests to the same bookie May 20, 2024
@yanliang567
Copy link
Contributor

@JamesBonddu is it the same issue with #32694? if yes, please offer logs and more info in that issue. thanks

/assign @JamesBonddu
/unassign

@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 20, 2024
@JamesBonddu
Copy link
Author

@JamesBonddu is it the same issue with #32694? if yes, please offer logs and more info in that issue. thanks

/assign @JamesBonddu /unassign

not same question, i also asked in pulsar .
image
image
image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

2 participants