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. |
||
|---|---|---|
| .. | ||
| common-issues | ||
| data | ||
| disk | ||
| snapshot | ||
| corruption-issues.asciidoc | ||
| discovery-issues.asciidoc | ||
| fix-common-cluster-issues.asciidoc | ||
| network-timeouts.asciidoc | ||
| troubleshooting-searches.asciidoc | ||
| troubleshooting-shards-capacity.asciidoc | ||