zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Flavio Junqueira <fpjunque...@yahoo.com.INVALID>
Subject Re: zookeeper shows two leaders after election
Date Tue, 15 Jul 2014 08:18:39 GMT
Hi Weide,

Consider upgrading to the 3.4 branch. Also, it is not a problem that two servers are in the
leader state, since only one will be able to make progress. To make progress, the leader needs
a majority of supporters.


On Tuesday, July 15, 2014 3:18 AM, Weide Zhang <weoccc@gmail.com> wrote:

>We are using zookeeper 3.3.4 in our production cluster with 5 machines with
>additional 4 observers for read traffic. We currently observe some weird
>behavior when zookeeper relects leader to another server, sometimes, the
>old zookeeper seems still in the state of LEADING (even though it
>disconnects the other followers) and new leader has been elected.  We could
>still see the following log message after the server loses leadership. And
>it causes observer to continuously connect to the server.  The session
>timeout for observer is set to 1 hour. (I'm not sure if it's relevant here
>INFO  [WorkerReceiver Thread:FastLeaderElection@496] - Notification: 5
>(n.leader), 1988571642783 (n.zxid), 535 (n.round), LEADING (n.state), 5
>(n.sid), LEADING (my state)
>Do you guys know any bugs for zookeeper 3.3.4 that could have this issue or
>how shall we debug this issue further ?
>Thanks a lot,
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message