[
https://issues.apache.org/jira/browse/HBASE-15504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205597#comment-15205597
]
Guanghao Zhang commented on HBASE-15504:
----------------------------------------
HBASE-14604 increase move cost when cluster regions number is bigger than
maxMoves. Before HBASE-14604, it scale move cost between [0,
cluster.numRegions] and it doesn't matter with maxMoves. But in our use case,
we config small maxMoves because we don't want move too much region on our
online serving cluster. HBASE-14604 will scale move cost between [0,
Math.min(cluster.numRegions, maxMoves)]. Do you mind to share your config about
maxMoves and cluster regions number?
> Fix Balancer in 1.3 not moving regions off overloaded regionserver
> ------------------------------------------------------------------
>
> Key: HBASE-15504
> URL: https://issues.apache.org/jira/browse/HBASE-15504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Elliott Clark
> Fix For: 1.3.0
>
>
> We pushed 1.3 to a couple of clusters. In some cases the regions were
> assigned VERY un-evenly and the regions would not move after that.
> We ended up with one rs getting thousands of regions and most servers getting
> 0. Running balancer would do nothing. The balancer would say that it couldn't
> find a solution with less than the current cost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
