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

Posted to issues@zookeeper.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/08/04 21:05:00 UTC

[jira] [Updated] (ZOOKEEPER-3492) Add weights to server side connection throttling

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

ASF GitHub Bot updated ZOOKEEPER-3492:
--------------------------------------
    Labels: pull-request-available  (was: )

> Add weights to server side connection throttling
> ------------------------------------------------
>
>                 Key: ZOOKEEPER-3492
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3492
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: Jie Huang
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>
> In ZOOKEEPER-3242, we introduced connection throttling to protect the server from being overloaded. We realize that the costs for creating a local session, creating a global session, and reconnecting are different. So we associate weights to the costs when throttling. For example, for the same setting, the throttler will allow more connections to be created if they are local.  This allows the server resources to be fully utilized.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)