-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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]: After Milvus recovered from standalone pod failure chaos, many interface responses became significantly slower, and listing collections directly resulted in errors #37828
Comments
/assign @weiliu1031 |
/assign |
/assign @czs007 |
span=90013 milliseconds = 90 seconds Kafka timed out, resulting in a significant channel CP lag. The Search uses Strong consistency, causing it to queue up, awaiting the advancement of tsafe. |
Saw big lag on kafka but didn't see any obvious resource racing. Need to rerun with metrics turned on /unassign @czs007 |
Is there an existing issue for this?
Environment
Current Behavior
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-kafka-cron/detail/chaos-test-kafka-cron/18586/pipeline
log:
artifacts-standalone-pod-failure-18586-server-logs.tar.gz
cluster: 4am
ns: chaos-testing
pod info
Anything else?
No response
The text was updated successfully, but these errors were encountered: