[
https://issues.apache.org/jira/browse/HBASE-29231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956211#comment-17956211
]
Hudson commented on HBASE-29231:
--------------------------------
Results for branch master
[build #1303 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1303/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1303/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1303/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.3.5 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1303/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.3.6 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1303/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.4.0 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1303/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
> Throttles should support limits based on handler thread usage time
> ------------------------------------------------------------------
>
> Key: HBASE-29231
> URL: https://issues.apache.org/jira/browse/HBASE-29231
> Project: HBase
> Issue Type: Improvement
> Reporter: Ray Mattingly
> Assignee: Ray Mattingly
> Priority: Major
> Labels: pull-request-available
>
> We can reference RpcCall#getStartTime when closing quotas to determine the
> processing time of any given operation.
> With this information, we could start throttling users based on the aggregate
> processing time of all of their requests — this could be a solid last line of
> defense for workloads that are deceptively expensive, and would make throttle
> configuration feel less like whack-a-mole.
> For example, let's say you run RegionServers with 100 handler threads. This
> means that, in any given second, you have 100,000 millis of handler thread
> time to spend on all of the workloads against your cluster. It could be great
> to restrict certain workloads to some smaller proportion of that time, so
> that you can guarantee there will always be processing time dedicated to
> other workloads.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
