When the leader is established there is a consensus decision on the start state of the ensemble (NEWLEADER message acts as the accept and UPTODATE message acts as commit). So all operations in the leader's log are acked by a quorum at that stage.
Alex On Tue, Jan 6, 2015 at 12:41 PM, Ibrahim <[email protected]> wrote: > Hi folks, > > This is really intersting post. It leads me to become more and more > confitable about Zab implementation. > > I just want to make sure in bit1129 second scanario "2. A,B,C starts first > Assume A is the leader since it has more recent transaction id, then the > whole quorum will have this write because B,C will sync with A. At last, > the whole quorum will have the write. > > In this scenario, we assume only one follower persist the operation and > ack, > meaning that the quorum has not reached because B and C didn't persist and > ack. > > Here I am really wondering how Zab can has such transaction replicated in > memory even the transaction has not got enough majority? > > Thank you > > Ibrahim > > > > > > > > -- > View this message in context: > http://zookeeper-user.578899.n2.nabble.com/Question-about-the-two-phrase-commit-tp7580725p7580736.html > Sent from the zookeeper-user mailing list archive at Nabble.com. >
