[
https://issues.apache.org/jira/browse/ZOOKEEPER-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713801#comment-13713801
]
Germán Blanco commented on ZOOKEEPER-1732:
------------------------------------------
It seems that the two servers in the enssemble are sending Notifications with a
different peerEpoch to the one out of the ensemble:
2013-07-19 10:17:00,833 [myid:1] - INFO
[WorkerReceiver[myid=1]:FastLeaderElection@542] - Notification: 3 (n.leader),
0xb800000099 (n.zxid), 0xb9 (n.round), FOLLOWING (n.state), 2 (n.sid), 0xb8
(n.peerEPoch), LOOKING (my state)
2013-07-19 10:17:00,833 [myid:1] - INFO
[WorkerReceiver[myid=1]:FastLeaderElection@542] - Notification: 3 (n.leader),
0xb900000052 (n.zxid), 0xba (n.round), LEADING (n.state), 3 (n.sid), 0xb9
(n.peerEPoch), LOOKING (my state)
Is that correct?
> ZooKeeper server unable to join established ensemble
> ----------------------------------------------------
>
> Key: ZOOKEEPER-1732
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1732
> Project: ZooKeeper
> Issue Type: Bug
> Components: leaderElection
> Affects Versions: 3.4.5
> Environment: Windows 7, Java 1.7
> Reporter: Germán Blanco
> Priority: Critical
> Attachments: zklog.tar.gz
>
>
> I have a test in which I do a rolling restart of three ZooKeeper servers and
> it was failing from time to time.
> I ran the tests in a loop until the failure came out and it seems that at
> some point one of the servers is unable to join the enssemble formed by the
> other two.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
