Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (nike.apache.org: domain of marcin.cabaj@datasift.com
 designates 209.85.192.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEH-zfrW1n2EwdwLazna4fv+w9e1f+pL2rtZx=QuZgzW0Dw0QA@mail.gmail.com>
References: 
 <CAO62+mEbMEWpQ3n72oZxM2o-1gT+4XaBTJmHK9ckxxtCVDpCWw@mail.gmail.com>
	<CAEH-zfrQ8p7DD46QmDq-p5mWoe-4sU-LB4XQFqwD6JQ8aGeb-g@mail.gmail.com>
	<CAEH-zfrW1n2EwdwLazna4fv+w9e1f+pL2rtZx=QuZgzW0Dw0QA@mail.gmail.com>
Date: Tue, 18 Feb 2014 15:04:27 +0000
Message-ID: 
 <CAO62+mH3JEQhAPk96ELxx3QpEBkUU_0fF1KSRs8zCiJSbtiEag@mail.gmail.com>
Subject: Re: how to fix messed up servers id
From: Marcin Cabaj <marcin.cabaj@datasift.com>
To: user@zookeeper.apache.org
Content-Type: multipart/alternative; boundary=001a11c13c80af031404f2af9618

--001a11c13c80af031404f2af9618
Content-Type: text/plain; charset=ISO-8859-1

Thanks, will try it tomorrow.
One thing I'm wondering, if I set zoo0 id to eg 5, should I update zoo.cfg
on other servers?
If so restart is needed as well right? It will crash my cluster. Or just
leave zoo.cfg as is?

-- 
cheers
mc


On Tue, Feb 18, 2014 at 1:41 PM, German Blanco <
german.blanco.blanco@gmail.com> wrote:

> For this step:
> "Set a different id in the myid file of server 0 (the one that is down),
> restart it, verify that it joins the quorum." any value that is not used
> should do, e.g. 3, 4, 5, 1231 ...
>
>
> On Tue, Feb 18, 2014 at 12:04 PM, German Blanco <
> german.blanco.blanco@gmail.com> wrote:
>
> > Hello!
> > Set a different id in the myid file of server 0 (the one that is down),
> > restart it, verify that it joins the quorum.
> > If it joins the quorum, set the myid value in server 1 to one, restart
> it,
> > verify that it joins the quorum.
> > If it joins the quorum, update again the myid file of server 0, this time
> > to the correct 0 value. Restart, verify that it all works.
> >
> > If any of the steps fails, stop and think it all over again.
> >
> > Good luck.
> >
> >
> > On Tuesday, February 18, 2014, Marcin Cabaj <marcin.cabaj@datasift.com>
> > wrote:
> >
> >> Hi all,
> >>
> >> My ZooKeeper ensemble contains 3 servers, unfortunately somehow servers
> >> ids
> >> have been messed up.
> >>
> >> zoo.cfg on all servers:
> >> server.0=zoo0:2888:3888
> >> server.1=zoo1:2888:3888
> >> server.2=zoo2:2888:3888
> >>
> >> but:
> >> on ZOO0:
> >> [xxx@zoo0]$ cat /var/zookeeper/myid
> >> 1
> >> [xxx@zoo0]$ echo conf | nc localhost 2181
> >> This ZooKeeper instance is not currently serving requests
> >>
> >> on ZOO1:
> >> [xxx@zoo1] $ cat /var/zookeeper/myid
> >> 0
> >> [xxx@zoo1:~]$ echo conf | nc localhost 2181 | grep serverId
> >>
> >> serverId=0
> >>
> >> on ZOO2:
> >> [xxx@zoo2:~]$ cat /var/zookeeper/myid
> >> 2
> >> [xxx@zoo2:~]$ echo conf | nc localhost 2181 | grep serverId
> >> serverId=2
> >>
> >> How to fix this without shutting down whole ensemble?
> >> Currently I have connections established to ZOO1 and ZOO2.
> >> ZOO0 is listening on 2181 but doesn't accept connections.
> >> ZOO2 is the leader.
> >>
> >> Zookeeper version: 3.3.5-cdh3u5--1, built on 10/06/2012 01:58 GMT
> >>
> >> Cheers
> >>
> >
>

--001a11c13c80af031404f2af9618--