[
https://issues.apache.org/jira/browse/ZOOKEEPER-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719483#comment-13719483
]
Germán Blanco commented on ZOOKEEPER-1732:
------------------------------------------
The proposal meant to set the election epoch to the same value during the
initial phase of the Zab protocol. That "same value" would be the proposed
epoch in the LEADERINFO structure. As you say, it is a change in the protocol,
even if messages have the same information. And it wouldn't work if there are
servers in the quorum with different behaviours (e.g. 3.4.5 and 3.4.6 with this
change implemented), since they will end up reporting different election epoch.
I hope loosening the constrain works, that would really be an easy solution :-)
> 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: Blocker
> Fix For: 3.5.0, 3.4.6
>
> 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
