If an operation is logged to disk on a minority of servers, then what happens on restart depends on which server wins the leader election. Since the new operation is on a minority, depending on network conditions, a server that did *not* log the operation might win the leader election. In this case, the operation will be discarded. If a server that *did* log the operation wins the leader election (as would be the case in the absence of network or latency issues), then the operation will be propagated to the remaining servers in the ensemble.
Edward On Jan 6, 2015, at 3:42 PM, Ibrahim <[email protected]> wrote: > Hi Alexander, > > So, you meant that if there is operation loged to the disk but it hasn't got > enough majority, then if the zookeeper servers restart, the new leader will > re-broadcast the loged operation again to the followers to commit that > operation. > > Does above what you meant by (NEWLEADER message acts as the accept and > UPTODATE message acts as commit). > > Am I right? > > Thank you > > Ibrahim > > > > -- > View this message in context: > https://urldefense.proofpoint.com/v1/url?u=http://zookeeper-user.578899.n2.nabble.com/Question-about-the-two-phrase-commit-tp7580725p7580739.html&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=09h%2FR60Z1NzKuJcTv9DkEw%3D%3D%0A&m=T7mEM8unY7tsVTbHXoSOqvwXEZEBCs8%2BRWl0cT03ruo%3D%0A&s=bcce5c88300c51126777473143b3f560542cf1c5699b33283f888e27ed41529f > Sent from the zookeeper-user mailing list archive at Nabble.com.
