Unassigned Primary and Replica Shard


I have a 4 machine cluster (2 data nodes and 2 master nodes) and some time
last night I had a failover from one master to the other. At this time a
number of things happened:

  1. Original master came back up but did not join the cluster
  2. Shards for about 5 indexes are unassigned and now report that they
    have 0 documents in this.

Case 2 is much more worrying as I'm loosing data. Does anyone have insight
of why this happens? How can it be avoided?

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/187c35cc-0472-4403-bc03-23db451e9106%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.