You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2019/09/05 21:44:00 UTC
[jira] [Commented] (ZOOKEEPER-3492) Add weights to server side
connection throttling
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923755#comment-16923755 ]
Hudson commented on ZOOKEEPER-3492:
-----------------------------------
SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #680 (See [https://builds.apache.org/job/ZooKeeper-trunk/680/])
ZOOKEEPER-3492: Add weights to server side connection throttling (hanm: rev eecd9e7ce046083bd40cd6134bdb2b405d01fe67)
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/SessionTrackerImpl.java
* (edit) zookeeper-server/src/test/java/org/apache/zookeeper/server/PrepRequestProcessorTest.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/ZooKeeperServer.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/BlueThrottle.java
* (edit) zookeeper-server/src/test/java/org/apache/zookeeper/server/BlueThrottleTest.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/SessionTracker.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/quorum/UpgradeableSessionTracker.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/quorum/LeaderSessionTracker.java
* (edit) zookeeper-docs/src/main/resources/markdown/zookeeperAdmin.md
> 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
> Assignee: Jie Huang
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.6.0
>
> Time Spent: 1h 50m
> 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)