[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903065#action_12903065
 ] 

Travis Crawford commented on ZOOKEEPER-856:
-------------------------------------------

@mahadev - I would love to help test a patch :) I'm currently using 3.3.1 + 
ZOOKEEPER-744 + ZOOKEEPER-790, applied in that order.

If there's a knob for how frequently to disconnect/reconnect I can try out 
different settings to see what a sensible default would be.

Do you think this should be a client or server setting? I'm thinking a server 
setting because otherwise its not possible to enforce the policy.

> 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
>             Fix For: 3.4.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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to