> ElasticSearch has implemented its own distributed coordination and is susceptible to such issues.
Only if configured wrong: setting discovery.zen.minimum_master_nodes to N/2 + 1 where N is the number of master nodes in the cluster prevents split-brain. Nodes that don't see enough master nodes will go into a catatonic state and won't accept writes, effectively preventing a split-brain syndrome.
Comments
> ElasticSearch has implemented its own distributed coordination and is susceptible to such issues.
Only if configured wrong: setting discovery.zen.minimum_master_nodes to N/2 + 1 where N is the number of master nodes in the cluster prevents split-brain. Nodes that don't see enough master nodes will go into a catatonic state and won't accept writes, effectively preventing a split-brain syndrome.
That's only sufficient if your network is perfectly reliable. Otherwise, you can still get split-brain in situations like this:
https://github.com/elasticsearch/elasticsearch/issues/2488
This particular bug is probably fixable, but reaching consensus on a set of master nodes in the general case, without race conditions, is quite hard.