[ 
https://issues.apache.org/jira/browse/HBASE-25621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322504#comment-17322504
 ] 

Hudson commented on HBASE-25621:
--------------------------------

Results for branch branch-2.2
        [build #205 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/205/]:
 (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.2/205//General_Nightly_Build_Report/]




(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.2/205//JDK8_Nightly_Build_Report_(Hadoop2)/]


(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.2/205//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for 
details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/205//artifact/output-integration/hadoop-2.log].
 (note that this means we didn't run on Hadoop 3)


> Balancer should check region plan source to avoid misplace region groups
> ------------------------------------------------------------------------
>
>                 Key: HBASE-25621
>                 URL: https://issues.apache.org/jira/browse/HBASE-25621
>             Project: HBase
>          Issue Type: Improvement
>          Components: Balancer
>            Reporter: Xiaolin Ha
>            Assignee: Xiaolin Ha
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.2.7, 2.5.0, 2.3.5, 2.4.3
>
>
> Currently, balancer generates all group plans firstly, and then execute 
> overall plans. When there are table regions movement between groups but after 
> the groups plans generating and before executing, balancer may misplace the 
> region to the old group. But this is not serious problem, next balancer will 
> fix it. 
> If we add a check before executing balance plans, we can avoid the problem. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to