[
https://issues.apache.org/jira/browse/ZOOKEEPER-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Peon updated ZOOKEEPER-1814:
-----------------------------------
Attachment: patch-zk-1814.patch
I attached a patch where the parameter maxNotificationInterval keeps its
default value defined in FastLeaderElection source file, but also it is
possible to configure the value of this parameter by using the configuration
file.
It is possible to find in the patch: source code modifications; a new test case
that proves the configuration of the parameter (it can be tested that the test
case fails if the source code modifications are deleted); a modification in the
QuorumPeerMain test case which failed from time to time due to the value of
this parameter; and the modifications in the Administration's Guide indicating
the configurable parameter.
> 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: patch-zk-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.1.4#6159)
