In our system we have had a communications problem that has generated an
error Split Brain, two master nodes within the same cluster share the
same nodes.
In GitHub describe this problem in the Link:
Did this corrected this case in some later version 0.90.5?
The current approach used to fix split brain problems by the Elasticsearch
is not to correct the symptoms, but address the cause. Split brains occur
when one of more nodes becomes unavailable, usually due to out of memory
(constant GC), overwhelmed threads or network issues. The last one is hard
to avoid, but there have been improvements to help with memory and
threading. Do any of these cases apply to your situation?
Elasticsearch is improving the consensus/election algorithm in order to not
get into split brain situations, but in the mean time you should look into
avoid situations that caused it.
In our system we have had a communications problem that has generated an
error Split Brain, two master nodes within the same cluster share the
same nodes.
In GitHub describe this problem in the Link: https://github.com/elasticsearch/elasticsearch/issues/2488
Did this corrected this case in some later version 0.90.5?
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.