Yes split brains are bad and we can avoid it by setting discovery.zen.minimum_master_nodes to (n/2+1) quorums.  This question is to understand why Elasticsearch cannot attempt to reconcile/replay the diverged data when a cluster recovers back from split brain.

Yes, in case some documents have conflicting data, I understand there is data corruption but in many scenarios where documents on either halves have no conflicts, does Elasticsearch attempt to merge and reconcile the shards on the diverged halves?

If not that would be a cool feature to add but I am guessing this is not possible today. So I would love to understand more on what exactly happens when the cluster is coming out of a split brain and if I am right, why does Elasticsearch currently just discard all state from the half that was restarted (to join the other half)
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB