You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2016/09/22 09:55:20 UTC

[jira] [Commented] (ZOOKEEPER-2461) There is no difference between the observer and the participants in the leader election algorithm

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512803#comment-15512803 ] 

Flavio Junqueira commented on ZOOKEEPER-2461:
---------------------------------------------

I'm sorry for taking some time to respond [~nerdyyatrice]

bq. By that time, all the participants haven't agreed on the new leader so they all replied with the old leader.

This observation isn't correct. When a server transitions into looking, it sets the vote to itself, so those notifications indicating that they are supporting 4 in this round. It is possible that they are just electing the same leader because of some glitch in your instance.

> There is no difference between the observer and the participants in the leader election algorithm
> -------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2461
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2461
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: quorum
>    Affects Versions: 3.5.0
>            Reporter: Ryan Zhang
>            Assignee: Ryan Zhang
>             Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> We have observed a case that when a leader machine crashes hard, non-voting learners take a long time to detect the new leader. After looking at the details more carefully, we identified one potential improvement (and one bug fixed in the 3.5).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)