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]: [Nightly] Cluster pulsar ran too slow and failed for timeout(6h) #38260

Closed
1 task done
NicoYuan1986 opened this issue Dec 6, 2024 · 3 comments
Closed
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@NicoYuan1986
Copy link
Contributor

NicoYuan1986 commented Dec 6, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 6ff1948
- Deployment mode(standalone or cluster): cluster
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Cluster pulsar ran too slow and failed for timeout(6h).
link: https://jenkins.milvus.io:18080/blue/organizations/jenkins/Milvus%20Nightly%20CI(new)/detail/master/203/pipeline/156/
log: artifacts-milvus-distributed-streaming-service-mdss-master-203-py-n-203-e2e-logs.tar.gz

expect: finish in 3h30min
actual: 86% in 6h (no error, just slow)

Expected Behavior

pass

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@NicoYuan1986 NicoYuan1986 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 Dec 6, 2024
@NicoYuan1986 NicoYuan1986 added this to the 2.5.1 milestone Dec 6, 2024
@NicoYuan1986 NicoYuan1986 changed the title [Bug]: [Nightly] Streaming node ran too slow and failed for timeout(6h) [Bug]: [Nightly] Cluster pulsar ran too slow and failed for timeout(6h) Dec 6, 2024
@NicoYuan1986 NicoYuan1986 assigned congqixia and unassigned chyezh Dec 6, 2024
@NicoYuan1986
Copy link
Contributor Author

@congqixia Can you help take a look?

@binbinlv binbinlv added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 6, 2024
@binbinlv
Copy link
Contributor

binbinlv commented Dec 6, 2024

/unassign @yanliang567

@yanliang567
Copy link
Contributor

not reproduced recently

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/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

5 participants