[
https://issues.apache.org/jira/browse/HBASE-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890779#comment-15890779
]
Kahlil Oppenheimer edited comment on HBASE-17709 at 3/1/17 6:45 PM:
--------------------------------------------------------------------
Not sure why this build failed, but I resubmitted a patch and made sure it was
properly based off master. I can build locally and all tests pass locally
[~tedyu]
was (Author: kahliloppenheimer):
Not sure why this build failed, but I resubmitted a patch and made sure it was
properly based off master. I can build locally and all tests pass locally.
> 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, HBASE-17709-01.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)
