[Bug]: After the message queue component's pod is killed and recovered, all Milvus flush operations are timing out. #39197
Labels
feature/streaming node
streaming node feature
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Is there an existing issue for this?
Environment
Current Behavior
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
Both tests have enabled the streaming node.
kafka pod kill chaos test
failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-kafka-cron/detail/chaos-test-kafka-cron/19115/pipeline
log:
artifacts-kafka-pod-kill-19115-server-logs.tar.gz
pod info
pulsar pod kill chaos test
faild job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-cron/detail/chaos-test-cron/20120/pipeline
log:
artifacts-pulsar-pod-failure-20120-server-logs.tar.gz
Pulsar has a particular issue: after pod is killed, 2 out of 3 bookies fail to restart.
pod info
Anything else?
No response
The text was updated successfully, but these errors were encountered: