ddd4ba5e30
Today the `current_node` parameter is given in several sample requests illustrating how to explain an unassigned shard using the cluster allocation explain API. This doesn't make sense, an unassigned shard has no `current_node`. This commit removes the misleading parameter in these cases. |
||
|---|---|---|
| .. | ||
| allocation-explain.asciidoc | ||
| cluster-info.asciidoc | ||
| delete-desired-balance.asciidoc | ||
| delete-desired-nodes.asciidoc | ||
| get-desired-balance.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 | ||
| prevalidate-node-removal.asciidoc | ||
| remote-info.asciidoc | ||
| reroute.asciidoc | ||
| state.asciidoc | ||
| stats.asciidoc | ||
| tasks.asciidoc | ||
| update-desired-nodes.asciidoc | ||
| update-settings.asciidoc | ||
| voting-exclusions.asciidoc | ||