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. |
||
|---|---|---|
| .. | ||
| recipes | ||
| disk-usage.asciidoc | ||
| fix-common-cluster-issues.asciidoc | ||
| general.asciidoc | ||
| indexing-speed.asciidoc | ||
| knn-search.asciidoc | ||
| recipes.asciidoc | ||
| search-speed.asciidoc | ||
| size-your-shards.asciidoc | ||
| use-elasticsearch-for-time-series-data.asciidoc | ||