Hudson commented on HBASE-20133:

Results for branch master
        [build #259 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/259/]: (x) 
*{color:red}-1 overall{color}*
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 

(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 

(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 

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

> Calculate correct assignment and build region movement plans for mis-placed 
> regions in one pass
> -----------------------------------------------------------------------------------------------
>                 Key: HBASE-20133
>                 URL: https://issues.apache.org/jira/browse/HBASE-20133
>             Project: HBase
>          Issue Type: Improvement
>          Components: rsgroup
>            Reporter: Xiang Li
>            Assignee: Xiang Li
>            Priority: Minor
>             Fix For: 3.0.0
>         Attachments: HBASE-20133.master.000.patch, 
> HBASE-20133.master.001.patch, HBASE-20133.master.002.patch
> In RSGroupBasedLoadBalancer#balanceCluster(clusterState), the logic could be 
> improved:
> correctAssignment() builds a map for mis-placed and placed regions. For 
> mis-placed regions, the key(ServerName) is BOGUS_SERVER_NAME. Then the logic 
> gets those mis-paced regions out and calls findServerForRegion() several 
> times to find out the current host server, in order to build RegionPlan for 
> movement.
> Some logic in correctAssignment() and findServerForRegion() could be merged 
> so as to build both corrected assignment and RegionPlan for mis-placed region 
> in one pass. As a result, findServerForRegion() could be removed if I get it 
> correctly.

This message was sent by Atlassian JIRA

Reply via email to