mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
02f38e3da9
The cluster allocation explain API includes a top-level status indicating to the user whether the shard can be assigned/rebalanced/etc or not. Today this status is fairly terse and experience shows that users sometimes struggle to understand how to interpret it and to decide on follow-up actions. This commit makes the top-level explanation more detailed and actionable. For instance, in the cases like `THROTTLED` where the status is transient we instruct the user to wait; if a shard is lost we say to restore it from a snapshot; if a shard cannot be assigned we say to choose a specific node where its assignment is expected and to address the obstacles. Co-authored-by: James Rodewig <james.rodewig@elastic.co> |
||
|---|---|---|
| .. | ||
| allocation-explain.asciidoc | ||
| delete-desired-nodes.asciidoc | ||
| get-desired-nodes.asciidoc | ||
| get-settings.asciidoc | ||
| health.asciidoc | ||
| nodes-hot-threads.asciidoc | ||
| nodes-info.asciidoc | ||
| nodes-reload-secure-settings.asciidoc | ||
| nodes-stats.asciidoc | ||
| nodes-usage.asciidoc | ||
| pending.asciidoc | ||
| remote-info.asciidoc | ||
| reroute.asciidoc | ||
| state.asciidoc | ||
| stats.asciidoc | ||
| tasks.asciidoc | ||
| update-desired-nodes.asciidoc | ||
| update-settings.asciidoc | ||
| voting-exclusions.asciidoc | ||