[
https://issues.apache.org/jira/browse/HBASE-25836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339255#comment-17339255
]
Hudson commented on HBASE-25836:
--------------------------------
Results for branch branch-2.4
[build #109 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/109/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/109/General_20Nightly_20Build_20Report/]
(/) {color:green}+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.4/109/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.4/109/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/109/JDK11_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}
> RegionStates#getAssignmentsForBalancer should only care about OPEN or OPENING
> regions
> -------------------------------------------------------------------------------------
>
> Key: HBASE-25836
> URL: https://issues.apache.org/jira/browse/HBASE-25836
> Project: HBase
> Issue Type: Sub-task
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3
>
>
> RegionStates#getAssignmentsForBalancer is used by the HMaster to collect all
> regions of interest to the balancer for the next chore iteration. We check if
> a table is in disabled state to exclude regions that will not be of interest
> (because disabled regions are or will be offline) or are in a state where
> they shouldn't be mutated (like SPLITTING ). The current checks do not get to
> the point so are not comprehensive.
> We should filter out all regions that are not in OPEN or OPENING state when
> building the set of interesting regions for the balancer to consider. Only
> regions open (or opening) on the cluster are of interest to balancing
> calculations. Regions in all other states can be expected to not be of
> interest -- either offline (OFFLINE, or FAILED_*), not subject to balancer
> decisions now (SPLITTING, SPLITTING_NEW, MERGING, MERGING_NEW), or will be
> offline shortly (CLOSING) -- until at least the next chore iteration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
