[ https://issues.apache.org/jira/browse/HBASE-24628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215341#comment-17215341 ]
Hudson commented on HBASE-24628: -------------------------------- Results for branch branch-2 [build #78 on builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/78/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (x) {color:red}-1 general checks{color} -- For more information [see general report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/78/General_20Nightly_20Build_20Report/] (x) {color:red}-1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/78/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/78/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/] (x) {color:red}-1 jdk11 hadoop3 checks{color} -- For more information [see jdk11 report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/78/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/] (x) {color:red}-1 source release artifact{color} -- See build output for details. (x) {color:red}-1 client integration test{color} -- Something went wrong with this stage, [check relevant console output|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/78//console]. > Region normalizer now respects a rate limit > ------------------------------------------- > > Key: HBASE-24628 > URL: https://issues.apache.org/jira/browse/HBASE-24628 > Project: HBase > Issue Type: Improvement > Components: Normalizer > Affects Versions: 3.0.0-alpha-1, 2.4.0 > Reporter: Nick Dimiduk > Assignee: Nick Dimiduk > Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > There's no limits on the normalizer right now. It will iterate through the > tables one at a time until it's touched all tables. For any table, it > generates a complete plan and executes that plan in totality. > It would be nice to allow operators to configure some limits here. Off the > top of my head, the two metrics that might be interesting are {{split|merge > actions / hour}} or {{hfile mb volume / hour}}. Either way, we'd need to > track a little more metadata. -- This message was sent by Atlassian Jira (v8.3.4#803005)