[
https://issues.apache.org/jira/browse/HBASE-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064951#comment-13064951
]
Ted Yu commented on HBASE-862:
------------------------------
@Nicholas:
You can use hbase.balancer.max.balancing to specify the total amount of time
each balance() call can take.
Since that is a new parameter, we expect it not to be set normally. In that
case, we use half of hbase.balancer.period for this limit.
If balancing is limited, you would see the following in master log:
{noformat}
LOG.debug("No more balancing till next balance run;
maximumBalanceTime=" +
maximumBalanceTime);
{noformat}
> region balancing is clumsy
> --------------------------
>
> Key: HBASE-862
> URL: https://issues.apache.org/jira/browse/HBASE-862
> Project: HBase
> Issue Type: Bug
> Reporter: stack
>
> Daniel Leffel has an install of 500 regions on 4 nodes. He's running 0.2.0.
> On restart, load balancing is running while the 600 regions are being
> initially opened. Makes for churn. Load balancing should wait before it
> cuts in.
> Have also seen on occasion that it will not find equilibrium after a restart.
> Adding a node is catastrophic. >20% of the regions were closed and were
> taking the longest time to show up on the new server. I would think that the
> region balancing would work in more sophisticated and gradual manner.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
