[
https://issues.apache.org/jira/browse/ZOOKEEPER-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039762#comment-13039762
]
Vishal Kathuria commented on ZOOKEEPER-1075:
--------------------------------------------
I did not see 1 relinquish the leadership when I ran the repro. 1 continued to
think it was the leader and 2 continued to refuse accepting that and they
stayed in this state indefinitely (over an hour I think)
> Zookeeper Server cannot join an existing ensemble if the existing ensemble
> doesn't already have a quorum
> --------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1075
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1075
> Project: ZooKeeper
> Issue Type: Bug
> Components: leaderElection
> Affects Versions: 3.3.2
> Environment: Windows 7
> Reporter: Vishal Kathuria
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Here is the sequence of steps that reproduces the problem.
> On a 3 server ensemble,
> 1. Bring up two servers (say 1 and 2). Lets say 1 is leading.
> 2. Bring down 2
> 3. Bring up 2.
> 4. 2 gets a notification from 1 that it is leading but 2 doesn't accept it as
> a leader since it cannot find one other node that thinks 1 is the leader.
> So the ensemble gets stuck where 2 isn't following. If at this point, 3 comes
> up, then one of 2 & 3 will become a leader and 1 will keep thinking it is the
> leader.
> I am working on a patch to fix this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
