I tried manually moving the shards using cluster reroute API & it works,
just wanted to know if there is any setting which can help in below
Here are my steps: Simulating a production node down scenario due to
Our setup: 1.0 ES , windows, all indices have 4 shards & zero replicas.
node1 : master + data
node2 : data
node3 : data
start node1 & index some data
start node2 & continue indexing data.
----At this point the primary shards are split across 2 nodes evenly.
- stop node2 & continue indexing data.
---- cluster goes in red state. All node2 shards go in unassigned state.
---- Indexing errors with UnavailableShardsException for all node 2 shards.
----Following is seen for all node2 shards from node1 logs.
[2014-11-18 15:56:46,482][DEBUG][gateway.local ] [Lament]
[data]: not allocating, number_of_allocated_shards_found ,
- start node3 & continue indexing data.
---All shards from node1 gets further split & node3 also gets half of the
-- cluster remains in red state & continue to get with
UnavailableShardsException for all node 2 shards.
I tried various settings for "index.recovery.initial_shards" but none
My question in case if a node goes down abruptly, is there a way to
automatically route the unassigned primary shards to other nodes?
Any pointers on how to move the unassigned shards back to other nodes
without manual cluster route API?
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 email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d11027f7-3530-48bc-88e8-74826d95ddb5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.