-
Notifications
You must be signed in to change notification settings - Fork 24.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API to return info/details on why shards are in unassigned state #9471
Labels
:Distributed/Distributed
A catch all label for anything in the Distributed Area. If you aren't sure, use this one.
>feature
help wanted
adoptme
Comments
+1 |
For shard corruption where it cannot open the shard, it looks like the new API here will help #11545 |
Closing in favour of #14593 |
lcawl
added
:Distributed/Distributed
A catch all label for anything in the Distributed Area. If you aren't sure, use this one.
and removed
:Allocation
labels
Feb 13, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed/Distributed
A catch all label for anything in the Distributed Area. If you aren't sure, use this one.
>feature
help wanted
adoptme
For admins, it will be nice to have an API that will return info/details on why shards are in an unassigned state (eg. is it waiting in a queue to be assigned, is it not getting assigned because there are not enough nodes for the replicas, is it not getting assigned because the shard data is corrupted, etc..). Perhaps this can be added to the reroute API where we can issue an empty reroute request + dry_run + explain and get an explanation for the unassigned shards, etc..
The text was updated successfully, but these errors were encountered: