zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael K. Edwards (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-1814) Reduction of waiting time during Fast Leader Election
Date Wed, 21 Nov 2018 23:33:00 GMT

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

Michael K. Edwards commented on ZOOKEEPER-1814:
-----------------------------------------------

Is this applicable to the current branch-3.5?

> Reduction of waiting time during Fast Leader Election
> -----------------------------------------------------
>
>                 Key: ZOOKEEPER-1814
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1814
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: leaderElection
>    Affects Versions: 3.4.5, 3.5.0
>            Reporter: Daniel Peon
>            Assignee: Daniel Peon
>            Priority: Major
>             Fix For: 3.6.0, 3.5.5
>
>         Attachments: ZOOKEEPER-1814.patch, ZOOKEEPER-1814.patch, ZOOKEEPER-1814.patch,
ZOOKEEPER-1814.patch, ZOOKEEPER-1814.patch, ZOOKEEPER-1814.patch, ZOOKEEPER-1814.patch, ZOOKEEPER-1814.patch,
ZOOKEEPER-1814.patch, ZOOKEEPER-1814_release_3_5_0.patch, ZOOKEEPER-1814_trunk.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> FastLeader election takes long time because of the exponential backoff. Currently the
time is 60 seconds.
> It would be interesting to give the possibility to configure this parameter, like for
example for a Server shutdown.
> Otherwise, it sometimes takes so long and it has been detected a test failure when executing:
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.
> This test case waits until 30 seconds and this is smaller than the 60 seconds where the
leader election can be waiting for at the moment of shutting down.
> Considering the failure during the test case, this issue was considered a possible bug.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message