hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17709) New MoveCostFunction that respects MaxMovePercent
Date Tue, 28 Feb 2017 19:31:45 GMT

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

Hadoop QA commented on HBASE-17709:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 2m 2s {color} | {color:red}
Docker failed to build yetus/hbase:8d52d23. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12855196/HBASE-17709-00.patch
|
| JIRA Issue | HBASE-17709 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/5878/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


This message was automatically generated.



> New MoveCostFunction that respects MaxMovePercent
> -------------------------------------------------
>
>                 Key: HBASE-17709
>                 URL: https://issues.apache.org/jira/browse/HBASE-17709
>             Project: HBase
>          Issue Type: Bug
>          Components: Balancer
>    Affects Versions: 1.2.0
>         Environment: CentOS Derivative with a derivative of the 3.18.43 kernel. HBase
on CDH5.9.0 with some patches. HDFS CDH 5.9.0 with no patches.
>            Reporter: Kahlil Oppenheimer
>            Priority: Minor
>              Labels: patch
>         Attachments: HBASE-17709-00.patch
>
>
> The balancer does not fully respect the maxMovePercent configuration. 
> Specifically, if the number of regions being moved is less than 600, the balancer currently
allows that number of region moves regardless of what value is set for maxMovePercent.
> This patch fixes that behavior and simplifies the moveCost function as well. In addition,
this patch adds short-circuiting logic to the balancer to terminate early once the maximum
number of moves are reached (and assuming the new plan has enough of a cost improvement).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message