[Bug]: After Milvus recovered from many components failure chaos, search failed with an error message failed to search: segment lacks
#37703
Labels
kind/bug
Issues or changes related a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
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
collection name: Checker__w6D93jMU
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/18551/pipeline
log:
artifacts-etcd-followers-pod-failure-18551-server-logs.tar.gz
pod info:
failed job:https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-kafka-cron/detail/chaos-test-kafka-cron/18547/pipeline
log:
artifacts-querynode-pod-failure-18547-server-logs.tar.gz
pod info
This issue has appeared in many component chaos tests, including MinIO QueryNode, but Etcd Follower does not cause any Milvus component to restart, which is somewhat puzzling. This issue may occur even without chaos under certain concurrent request conditions.
Anything else?
This issue was not reproduced in the image
master-20241112-f5b06a3c-amd64
The text was updated successfully, but these errors were encountered: