ES: 0.20.4
3 VM’s configured as Master/Data each.
Node-1
node.rack_id: r1
cluster.routing.allocation.awareness.force.rack_id.values: r1,r2
cluster.routing.allocation.awareness.attributes: rack_id
Node-2
node.rack_id: r2
cluster.routing.allocation.awareness.force.rack_id.values: r1,r2
cluster.routing.allocation.awareness.attributes: rack_id
Node-3
node.rack_id: r1
cluster.routing.allocation.awareness.force.rack_id.values: r1,r2
cluster.routing.allocation.awareness.attributes: rack_id
In creating an index, ES does NOT allocate the shards+replicas as per rack
designation. They are intermixed across nodes as if no rack designation
exists. Now restart all the ES nodes and the shards are split across two
nodes and the replicas are on one, but never intermixed with primary.
Create a new index and the primary + replica’s are intermixed and do not
rebalance based on rack until all ES nodes are restarted.
Is this the expected behavior?
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.