A reconfiguration is treated similarly to other proposals for recovery purposes (of course commit is different in that it changes the configuration). You can see the paper <https://www.usenix.org/system/files/conference/atc12/atc12-final74.pdf> for details on how recovery works in principle, and if you have a specific question please feel free to ask.
On Mon, Sep 28, 2015 at 10:54 AM, Ibrahim El-sanosi (PGR) < i.s.el-san...@newcastle.ac.uk> wrote: > Yes, I am thinking of mixing an in-flight reconfiguration request with the > crashing servers example that you gave.... Not about how proposals, acks, > commits (i.e.: ZAB proper) work. > > Thank you > > -----Original Message----- > From: Raúl Gutiérrez Segalés [mailto:r...@itevenworks.net] > Sent: Monday, September 28, 2015 02:56 ص > To: user@zookeeper.apache.org > Subject: Re: Zab Failure scenario > > On 27 September 2015 at 10:12, Ibrahim El-sanosi (PGR) < > i.s.el-san...@newcastle.ac.uk> wrote: > > > Thank you Flavio for explanation. It really makes sense for me. > > > > > I'm not sure why you are assuming 3.4.6, though. Why is it relevant > > > for > > this question? > > > > I am assuming 3.4.6 because first I use this version, second I do not > > know about dynamic configuration 3.5.0 as it may have different > > solution for mentioned scenario. > > > > I don't think dynamic reconfiguration changes anything about how > proposals, acks, commits (i.e.: ZAB proper) work. Unless you are thinking > of mixing an in-flight reconfiguration request with the crashing servers > example that you gave.... > > > -rgs >
