... and make sure that there is no rubbish in the data dir of the new server.
On Tue, Nov 5, 2013 at 3:49 PM, German Blanco < [email protected]> wrote: > Hello Jae, > > I think that the answer to your question is "no, there is no benefit in a > rolling restart in that case". > If you remove a machine that was hosting a zookeeper server that was part > of a cluster, and replace it with a new machine, with a zookeeper server > running the same software version and listening on the same IP and ports, > then this new server will join the cluster, synchronize and start working > normally. > I wouldn't recommend to replace more than one server at a time, and I > think that it is better if the new server joins while the existing quorum > is stable (avoid leader elections while the new server joins, i.e. avoid > restarts or disconnections of the existing servers). > > Best regards, > > Germán. > > > On Tue, Nov 5, 2013 at 6:42 AM, Bae, Jae Hyeon <[email protected]> wrote: > >> Hi >> >> I read an article >> >> http://www.benhallbenhall.com/2011/07/rolling-restart-in-apache-zookeeper-to-dynamically-add-servers-to-the-ensemble/ >> >> My question is, even though failed hardware is replaced with the same IP >> address, do I need to do rolling restart for adding replaced hardware to >> the quorum? >> >> I am using zookeeper ver3.4.5. >> >> Thank you >> Best, Jae >> > >
