We noticed unwanted synchronisation behaviour using two nodes with
elasticsearch-1.3.4. The nodes got disconnected from each other after a
network failure and both started running their own cluster. One node got
new data pushed to it, the other didn't. After restarting the node that got
the most recent data, it joined up with the other one. This resulted in the
loss of all the new data from the master node since the network failure.
Is this expected behaviour? If so, how can we prevent this scenario from
occurring again?
We noticed unwanted synchronisation behaviour using two nodes with
elasticsearch-1.3.4. The nodes got disconnected from each other after a
network failure and both started running their own cluster. One node got
new data pushed to it, the other didn't. After restarting the node that got
the most recent data, it joined up with the other one. This resulted in the
loss of all the new data from the master node since the network failure.
Is this expected behaviour? If so, how can we prevent this scenario from
occurring again?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.