[Bug]: When the query node is rolling upgraded, with 3 replicas, the first two query nodes are upgraded quickly, but the third query node waits for 30 minutes before completing the upgrade. #36426
- Milvus version:2.4.3--> master-20240920-eb23e23c-amd64
- Deployment mode(standalone or cluster):mixcoord
- MQ type(rocksmq, pulsar or kafka):
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
Current Behavior
It can be inferred from the age of the query node that there was a 30-minute gap between the second query node being upgraded to the third query node being upgraded.
Is there an existing issue for this?
Environment
Current Behavior
It can be inferred from the age of the query node that there was a 30-minute gap between the second query node being upgraded to the third query node being upgraded.
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/rolling_update_for_operator_test_simple/detail/rolling_update_for_operator_test_simple/4975/pipeline log: artifacts-kafka-mixcoord-4975-server-logs.tar.gz
cluster: 4am ns: chaos-testing pod info before upgrading
after upgrading
Anything else?
No response