[
https://issues.apache.org/jira/browse/ZOOKEEPER-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955168#comment-13955168
]
Flavio Junqueira commented on ZOOKEEPER-1814:
---------------------------------------------
I possibly haven't made it clear that I'm suggesting we do a better job in the
change to the documentation. I think the text there is a bit thin and not
really explaining how it affects a deployment and why one should care about it.
bq. but we can detect a shutdown in few seconds instead of 1 minute in the
worst case.
Is this referring to tests or something else? If this is not referring to
tests, then I'm not sure how it helps to detect a shutdown faster.
bq. If someone's deployment is already working by using that 60 seconds
maximum time for any reason, I didn't want to modify the default behavior.
It makes sense.
> 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
>
> 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)
