MilvusClientException: no available shard leaders: channel not available #48973
Unanswered
Siddeshvr
asked this question in
Q&A and General discussion
Replies: 1 comment 11 replies
-
|
"no available shard leaders: channel not available" -------------- You might see this error if a querynode(acts as a shard leader) crashes or restarts. Milvus recovers after a query node crashes and cannot work for a few minutes, see the similar issue: #44521. Usually, OOM and defects are the major reasons for query node crashes, "no available shard leaders: channel not available" is a result, not the root cause. |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Environment
Milvus version: v2.6.12
Deployment mode(standalone or cluster): cluster
When we restart the MilvusDB instance to update any configurations like (CPU, RAM, Woodpecker configs), I have observed that MilvusDB is going down due to crash and below are the logs observed
Client logs :
Caused by: io.milvus.v2.exception.MilvusClientException: no available shard leaders: channel not available[channel=by-dev-rootcoord-dml_1_464388135381283799v7] ErrorCode: SERVER_ERROR, ServerCode: 503
Once again if all the nodes of the MilvusDB are restarted, the error logs stopped and service started working.
Why do we see this issue and during restart why MilvusDB is not able to restart all the nodes properly into the stable state ?
Could you please help me to check this issue
Beta Was this translation helpful? Give feedback.
All reactions