Docs: clarification of allocation awareness w.r.t. rack failures
Closes #11908
This commit is contained in:
parent
37bde56971
commit
41f8c96fed
|
@ -44,7 +44,9 @@ nodes.
|
|||
|
||||
Now, if we start two more nodes with `node.rack_id` set to `rack_two`,
|
||||
Elasticsearch will move shards across to the new nodes, ensuring (if possible)
|
||||
that the primary and replica shards are never in the same rack.
|
||||
that no two copies of the same shard will be in the same rack. However if `rack_two`
|
||||
were to fail, taking down both of its nodes, Elasticsearch will still allocate the lost
|
||||
shard copies to nodes in `rack_one`.
|
||||
|
||||
.Prefer local shards
|
||||
*********************************************
|
||||
|
|
Loading…
Reference in New Issue