You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2018/11/17 17:35:00 UTC
[jira] [Resolved] (ZOOKEEPER-3177) Refactor request throttle logic
in NIO and Netty to keep the same behavior and make the code easier to
maintain
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Han resolved ZOOKEEPER-3177.
------------------------------------
Resolution: Fixed
Issue resolved by pull request 673
[https://github.com/apache/zookeeper/pull/673]
> 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: 1h 50m
> 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)