-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Open
Labels
kind/bugIssues or changes related a bugIssues or changes related a bugneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
Milestone
Description
Is there an existing issue for this?
- I have searched the existing issues
Environment
- Milvus version:
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:Current Behavior
When we merge all coordinator, the logic has been changed to only check rootcood.
This PR:
- add back the check for all coordinators
- for all node, only check and make sure there is node and all the node is healthy
Expected Behavior
No response
Steps To Reproduce
Milvus Log
No response
Anything else?
No response
Metadata
Metadata
Assignees
Labels
kind/bugIssues or changes related a bugIssues or changes related a bugneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.