You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Fengnan Li (Jira)" <ji...@apache.org> on 2020/01/09 06:29:00 UTC
[jira] [Commented] (ZOOKEEPER-856) Connection imbalance leads to
overloaded ZK instances
[ https://issues.apache.org/jira/browse/ZOOKEEPER-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011471#comment-17011471 ]
Fengnan Li commented on ZOOKEEPER-856:
--------------------------------------
[~eolivelli] I saw you are tagging this fix to be in the version zk 3.7.0, is there a patch already somewhere? We are facing similar issues here. Thanks!
> 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
> Priority: Major
> Fix For: 3.5.7, 3.7.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
(v8.3.4#803005)