Question related to pacificA: Elasticsearch's replication protocal


(Makeyang) #1

according to section of "Change of Primary" of paper:
"During reconciliation, p sends prepare messages for uncommitted requests in its prepared list and have them committed on the new configuration"
assume below scenario:
primary sends a update request(we call it RN) with its configuration version and the serial number in a prepare message to all replicas and network partition happens, some replicas get this prepare message and put it into their prepared list while othres not.
the old master will acked failed to client.
then one secondary which get RN get master lease and "sends prepare messages for uncommitted requests in its prepared list and have them committed on the new configuration"
by accidently, although the system achieve consistency, but the system have the date it shouldn't have.
do I miss something?


(system) #2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.