[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186708#comment-14186708
 ] 

Daniel Peon commented on ZOOKEEPER-1814:
----------------------------------------

Ok, I'll adapt the patch to trunk branch and I'll test it for 3.5 branch also.

The change that I commented above about the FLETestUtils.java file corresponds 
to the revision: 1608648

>>Revision: 1608648
>>Author: michim
>>Date: martes, 08 de julio de 2014 5:25:56
>>Message:
>>ZOOKEEPER-1810. Add version to FLE notifications for trunk Germán Blanco via 
>>michim)

If I can change the visibility of the class it will be easy the adaption of the 
test case.

Thanks in advance and regards.


> 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.4.7, 3.5.1, 3.6.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, 
> 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)

Reply via email to