You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/03/13 16:22:01 UTC
[jira] [Updated] (ZOOKEEPER-856) Connection imbalance leads to
overloaded ZK instances
[ https://issues.apache.org/jira/browse/ZOOKEEPER-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Han updated ZOOKEEPER-856:
----------------------------------
Fix Version/s: (was: 3.5.3)
3.5.4
> Connection imbalance leads to overloaded ZK instances
> -----------------------------------------------------
>
> Key: ZOOKEEPER-856
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-856
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Travis Crawford
> Assignee: Mahadev konar
> Fix For: 3.5.4, 3.6.0
>
> Attachments: zk_open_file_descriptor_count_members.gif, zk_open_file_descriptor_count_total.gif
>
>
> We've experienced a number of issues lately where "ruok" requests would take upwards of 10 seconds to return, and ZooKeeper instances were extremely sluggish. The sluggish instance requires a restart to make it responsive again.
> I believe the issue is connections are very imbalanced, leading to certain instances having many thousands of connections, while other instances are largely idle.
> A potential solution is periodically disconnecting/reconnecting to balance connections over time; this seems fine because sessions should not be affected, and therefore ephemaral nodes and watches should not be affected.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)