[ https://issues.apache.org/jira/browse/ZOOKEEPER-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808322#comment-13808322 ]
Germán Blanco commented on ZOOKEEPER-1732: ------------------------------------------ Yes, I am. Thank you for the correction. If you replace "round" with "peerEpoch" in my comment I think that it will make sense. Should we do this in a new JIRA then? If so, then I can prepare a patch on the current trunk and branch 3.4 and test the rolling upgrade. Although I don't like too much the idea of leaving the patches in this JIRA without the correction. The changes are very straightforward: - remove the changes in Leader.java - Change the line in Learner.java to: "self.updateElectionVote(newEpoch-1);" > 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 > Assignee: Germán Blanco > Priority: Blocker > Fix For: 3.4.6, 3.5.0 > > Attachments: CREATE_INCONSISTENCIES_patch.txt, zklog.tar.gz, > ZOOKEEPER-1732-3.4.patch, ZOOKEEPER-1732-3.4.patch, ZOOKEEPER-1732-3.4.patch, > ZOOKEEPER-1732-3.4.patch, ZOOKEEPER-1732-b3.4.patch, > ZOOKEEPER-1732-b3.4.patch, ZOOKEEPER-1732.patch, ZOOKEEPER-1732.patch, > ZOOKEEPER-1732.patch, ZOOKEEPER-1732.patch, ZOOKEEPER-1732.patch > > > 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 was sent by Atlassian JIRA (v6.1#6144)