[ https://issues.apache.org/jira/browse/ZOOKEEPER-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Han resolved ZOOKEEPER-3492. ------------------------------------ Resolution: Fixed Issue resolved by pull request 1037 [https://github.com/apache/zookeeper/pull/1037] > 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 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > 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 (v8.3.2#803003)