[
https://issues.apache.org/jira/browse/ZOOKEEPER-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715130#comment-13715130
]
Germán Blanco commented on ZOOKEEPER-1732:
------------------------------------------
If I am not wrong, the follower that is stuck never accepts the leadership of
the Leader in the ensemble, because it is an established ensemble and it sees
no quorum in it. So it will only send notifications proposing itself as the
leader. And the leader of the ensemble sends the Notifications only to the
follower that is stuck, or? So there is actually no chance for the stale
follower to receive the updated leader election information after the initial
election is finished.
I agree that one must be careful when changing network protocols and dealing
with backwards compatibility, but if you asked me, I think that it is much
easier to make mistakes doing multithreaded concurrent Java programming :-P
> 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
