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

Hudson commented on ZOOKEEPER-3177:
-----------------------------------

SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #271 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/271/])
ZOOKEEPER-3177: Refactor request throttle logic in NIO and Netty to keep (hanm: 
rev db074423f09026446640242ecfcf26310467b1fa)
* (edit) 
zookeeper-server/src/main/java/org/apache/zookeeper/server/ServerCnxn.java
* (edit) 
zookeeper-server/src/main/java/org/apache/zookeeper/server/quorum/LeaderZooKeeperServer.java
* (edit) 
zookeeper-server/src/main/java/org/apache/zookeeper/server/NettyServerCnxn.java
* (edit) 
zookeeper-server/src/main/java/org/apache/zookeeper/server/DumbWatcher.java
* (edit) 
zookeeper-server/src/main/java/org/apache/zookeeper/server/quorum/FollowerZooKeeperServer.java
* (edit) 
zookeeper-server/src/test/java/org/apache/zookeeper/server/MockServerCnxn.java
* (edit) 
zookeeper-server/src/main/java/org/apache/zookeeper/server/ZooKeeperServer.java
* (edit) 
zookeeper-server/src/main/java/org/apache/zookeeper/server/NIOServerCnxn.java


> Refactor request throttle logic in NIO and Netty to keep the same behavior 
> and make the code easier to maintain
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-3177
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3177
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: Fangmin Lv
>            Assignee: Fangmin Lv
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> There is shouldThrottle logic in zkServer, we should use it in NIO as well, 
> refactor the code to make it cleaner and easier to maintain in the future.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to