[
https://issues.apache.org/jira/browse/ZOOKEEPER-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823538#comment-13823538
]
Flavio Junqueira commented on ZOOKEEPER-1814:
---------------------------------------------
Thanks for reporting this issue. The 60 seconds you're referring to is the
worst case. Making the top interval configurable is not a bug, so it should go
into 3.5.0. If you want to bump the test case timeout value because it causes
failures, then please do it in a different jira. In any case, it is odd that
the test even hits the 60s limit. I think it is premature to blame the 60s
limit for the test failure.
> Reduction of time during 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
> Fix For: 3.5.0
>
> 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.1#6144)
