Skip to content

[DOCS] Use same index in Cluster Allocation Explain docs #50936

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jrodewig merged 1 commit into from
Jan 16, 2020
Merged

[DOCS] Use same index in Cluster Allocation Explain docs #50936

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 15 additions & 8 deletions docs/reference/cluster/allocation-explain.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,14 +103,21 @@ GET /_cluster/allocation/explain

===== Examples of unassigned primary shard explanations

//////
[source,console]
--------------------------------------------------
DELETE myindex
--------------------------------------------------
//////

[source,console]
--------------------------------------------------
PUT /idx?master_timeout=1s&timeout=1s
PUT /my_index?master_timeout=1s&timeout=1s
{"settings": {"index.routing.allocation.include._name": "non_existent_node"} }

GET /_cluster/allocation/explain
{
"index": "idx",
"index": "my_index",
"shard": 0,
"primary": true
}
Expand All @@ -122,7 +129,7 @@ The API returns the following response for an unassigned primary shard:
[source,console-result]
--------------------------------------------------
{
"index" : "idx",
"index" : "my_index",
"shard" : 0,
"primary" : true,
"current_state" : "unassigned", <1>
Expand Down Expand Up @@ -171,7 +178,7 @@ allocated to a node in the cluster:
[source,js]
--------------------------------------------------
{
"index" : "idx",
"index" : "my_index",
"shard" : 0,
"primary" : true,
"current_state" : "unassigned",
Expand All @@ -196,7 +203,7 @@ allocation:
[source,js]
--------------------------------------------------
{
"index" : "idx",
"index" : "my_index",
"shard" : 0,
"primary" : false,
"current_state" : "unassigned",
Expand Down Expand Up @@ -232,7 +239,7 @@ allocation:
{
"decider" : "same_shard",
"decision" : "NO",
"explanation" : "the shard cannot be allocated to the same node on which a copy of the shard already exists [[idx][0], node[3sULLVJrRneSg0EfBB-2Ew], [P], s[STARTED], a[id=eV9P8BN1QPqRc3B4PLx6cg]]"
"explanation" : "the shard cannot be allocated to the same node on which a copy of the shard already exists [[my_index][0], node[3sULLVJrRneSg0EfBB-2Ew], [P], s[STARTED], a[id=eV9P8BN1QPqRc3B4PLx6cg]]"
}
]
}
Expand All @@ -253,7 +260,7 @@ its current node and is required to move:
[source,js]
--------------------------------------------------
{
"index" : "idx",
"index" : "my_index",
"shard" : 0,
"primary" : true,
"current_state" : "started",
Expand Down Expand Up @@ -302,7 +309,7 @@ because moving the shard to another node does not form a better cluster balance:
[source,js]
--------------------------------------------------
{
"index" : "idx",
"index" : "my_index",
"shard" : 0,
"primary" : true,
"current_state" : "started",
Expand Down