You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2011/06/15 08:47:47 UTC

[jira] [Updated] (ZOOKEEPER-522) zookeeper client should throttle if its not able to connect to any of the servers.

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

Mahadev konar updated ZOOKEEPER-522:
------------------------------------

    Fix Version/s:     (was: 3.4.0)
                   3.5.0

not a blocker. Moving it out of 3.4 release.

> zookeeper client should throttle if its not able to connect to any of the servers.
> ----------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-522
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-522
>             Project: ZooKeeper
>          Issue Type: Improvement
>    Affects Versions: 3.2.0
>            Reporter: Mahadev konar
>             Fix For: 3.5.0
>
>
> Currently the zookeeper client library keeps connecting to servers if all of them are unreachable. It will go through the list time and again and try to connect. Sometimes, this might cause problems like too many clients retrying connect to servers (and there might be something wrong/delay with servers) wherein the clients will give up and will try reconnecting to other servers. This causes a huge churn in client connections sometimes leading to the zookeeper server running out of file handles.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira