Skip to content
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

Closed
ppf2 opened this issue Jan 28, 2015 · 3 comments
Closed

API to return info/details on why shards are in unassigned state #9471

ppf2 opened this issue Jan 28, 2015 · 3 comments
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

@ppf2
Copy link
Member

ppf2 commented Jan 28, 2015

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..

@runningman84
Copy link

+1

@ppf2
Copy link
Member Author

ppf2 commented Aug 7, 2015

For shard corruption where it cannot open the shard, it looks like the new API here will help #11545

@clintongormley
Copy link

Closing in favour of #14593

@lcawl 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
Projects
None yet
Development

No branches or pull requests

4 participants