[
https://issues.apache.org/jira/browse/ZOOKEEPER-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186697#comment-14186697
]
Flavio Junqueira commented on ZOOKEEPER-1814:
---------------------------------------------
if we are going to include this feature at all, then I'd say that having a
trunk patch makes sense (a 3.5 branch patch as well). Could you check with svn
blame which jira caused the modification you observed?
> 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.1
>
> 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
>
> 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.3.4#6332)
