You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Daniel Peon (JIRA)" <ji...@apache.org> on 2014/04/02 09:55:16 UTC
[jira] [Updated] (ZOOKEEPER-1814) Reduction of waiting time during
Fast Leader Election
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Peon updated ZOOKEEPER-1814:
-----------------------------------
Attachment: ZOOKEEPER-1814.patch
Modified the documentation according the provided comments. Documentation of the introduced configurable parameter was poor and it is explained better in this version.
> 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
> Fix For: 3.5.0
>
> 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
>
> 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
(v6.2#6252)