[
https://issues.apache.org/jira/browse/ZOOKEEPER-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714986#comment-13714986
]
Flavio Junqueira commented on ZOOKEEPER-1732:
---------------------------------------------
bq. My personal preference would be "3". Because it is faster (follower doesn't
go back to LOOKING, it can just update the proposal with the info in LeaderInfo)
I guess my description was not clear for 3. The idea was that the learner sends
its LE info so that the leader can drop it if the learner info is stale, so the
follower goes back to looking in this option as well.
I'm not worried about making this case fast because this is such a corner case:
a follower f elects a leader l, l crashes, l comes back, l is re-elected by a
quorum that does not include f, f is able to connect to connect to l.
> 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
