zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andor Molnar (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (ZOOKEEPER-3398) Learner.connectToLeader() may take too long to time-out
Date Mon, 15 Jul 2019 11:11:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andor Molnar reassigned ZOOKEEPER-3398:
---------------------------------------

    Assignee: Vladimir Ivić

> 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ć
>            Assignee: Vladimir Ivić
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>          Time Spent: 5h 10m
>  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)

Mime
View raw message