Hi ES team, When split-brain occurs, I found following behaviors on ES during the merge between A and B (i.e., a group of nodes with master A or B): Assume we don't know when the split-brain happens and both node groups have updated their data to some extends: - If A and B have exclusive data separately, all data will be merged successfully - If A and B have the same record id but different record value (due to update), ES cannot merge the data and the system is hanging there (aka. split-brain effect)
For the 2nd case, is it possible to add a customized merging strategy in ES? Say, *if having the same record id but different record value, we take the record with the latest timestamp*. By this means, I believe we will have less impact from split-brain. Can we do that? Or will it be added to ES roadmap. Thanks, Jing -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5a0515c4-d4dc-4062-a306-775317ec646f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
