[
https://issues.apache.org/jira/browse/HBASE-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008673#comment-13008673
]
Ted Yu commented on HBASE-3422:
-------------------------------
Summary of chat with Stack on IRC (see http://pastebin.com/4uK9M1Z7):
Since it is difficult to estimate the appropriate number of regions to balance
in one invocation of balance(), I resort to respecting the hbase.balancer.period
Another option would be to limit execution time of balance() to certain
percentage of hbase.balancer.period
But that would introduce another parameter which complicates our scenario.
> Balancer will try to rebalance thousands of regions in one go; needs an upper
> bound added.
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-3422
> URL: https://issues.apache.org/jira/browse/HBASE-3422
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 0.90.0
> Reporter: stack
> Assignee: Ted Yu
> Attachments: hbase-3422.txt
>
>
> See HBASE-3420. Therein, a wonky cluster had 5k regions on one server and <
> 1k on others. Balancer ran and wanted to redistribute 3k+ all in one go.
> Madness.
> If a load of rebalancing to be done, should be done somewhat piecemeal. We
> need maximum regions to rebalance at a time upper bound at a minimum.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
