-
Notifications
You must be signed in to change notification settings - Fork 3k
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]: [benchmark][cluster] Milvus is stuck and the client has no response #38609
Comments
/assign @sunby |
/assign @aoiasd |
But rootcoord works success, so seems dispatcher or msgstream has some problem. |
Another question was that our querynode tt lag metric report by sub time now and msg tt and label it by collection id, this will cause it looks like healthy when one channel consume stuck but others still work. |
different case,same problemargo task:weekly-stab-1735430400 server:
client requests have no responses logs:
test result:
|
different case,same problemargo task:weekly-stab-1735430400 server:
client log:
test result:
|
@aoiasd |
Is there an existing issue for this?
Environment
Current Behavior
argo task: fouramf-46vpj
server:
The following requests have no response
client logs:
Expected Behavior
No response
Steps To Reproduce
Milvus Log
No response
Anything else?
server config:
client config: fouramf-client-all-vector-types-dql-ddl
The text was updated successfully, but these errors were encountered: