mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 15:47:23 -04:00
95edc6deb2
Today we often encounter users that are confused by the behaviour of calling `GET _cluster/allocation/explain` without a body: it _seems_ to work, but it explains a random shard, and if this isn't the shard they're thinking of then it's unclear how to proceed. With this commit we add a note to the response when a shard was randomly chosen indicating that it is possible, and possibly useful, to explain a different shard. We also adjust the exception message in the case when all shards are assigned to indicate why it's an invalid request and what to do to make it valid. |
||
|---|---|---|
| .. | ||
| allocation-explain.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-settings.asciidoc | ||
| voting-exclusions.asciidoc | ||