You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Andor Molnar (JIRA)" <ji...@apache.org> on 2019/07/12 15:03:00 UTC
[jira] [Resolved] (ZOOKEEPER-3398) Learner.connectToLeader() may
take too long to time-out
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andor Molnar resolved ZOOKEEPER-3398.
-------------------------------------
Resolution: Fixed
Issue resolved by pull request 953
[https://github.com/apache/zookeeper/pull/953]
> Learner.connectToLeader() may take too long to time-out
> --------------------------------------------------------
>
> Key: ZOOKEEPER-3398
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3398
> Project: ZooKeeper
> Issue Type: Improvement
> Components: leaderElection, quorum
> Reporter: Vladimir Ivić
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.6.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> After leader election happens, the followers will connect to the leader which is facilitated by the Learner.connectToLeader() method.
> Learner.connectToLeader() is relying on the initLimit configuration value to time-out in case the network connection is unreliable. This config may have a high value that could leave the ensemble retrying and waiting in the state of not having quorum for too long. The follower will retry up to 5 times.
> This patch introduces a new configuration directive that will allow Zookeeper to use different time-out value `connectToLeaderLimit` which then could be set to lower value than `initLimit`.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)