[ https://issues.apache.org/jira/browse/HBASE-28346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887778#comment-17887778 ]
Hudson commented on HBASE-28346: -------------------------------- Results for branch branch-2.6 [build #217 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/217/]: (x) *{color:red}-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/branch-2.6/217/General_20Nightly_20Build_20Report/] (/) {color:green}+1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/217/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/] (/) {color:green}+1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/217/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/] (/) {color:green}+1 jdk11 hadoop3 checks{color} -- For more information [see jdk11 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/217/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/] (x) {color:red}-1 jdk17 hadoop3 checks{color} -- For more information [see jdk17 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/217/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{color} > Expose checkQuota to Coprocessor Endpoints > ------------------------------------------ > > Key: HBASE-28346 > URL: https://issues.apache.org/jira/browse/HBASE-28346 > Project: HBase > Issue Type: Improvement > Reporter: Bryan Beaudreault > Assignee: Charles Connell > Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1 > > > Coprocessor endpoints may do non-trivial amounts of work, yet quotas do not > throttle them. We can't generically apply quotas to coprocessors because we > have no information on what a particular endpoint might do. One thing we > could do is expose checkQuota to the RegionCoprocessorEnvironment. This way, > coprocessor authors have the tools to ensure that quotas cover their > implementations. > While adding this, we can update AggregationImplementation to call checkQuota > since those endpoints can be quite expensive. -- This message was sent by Atlassian Jira (v8.20.10#820010)