[
https://issues.apache.org/jira/browse/HBASE-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-3422.
--------------------------
Resolution: Fixed
Fix Version/s: 0.92.0
Hadoop Flags: [Reviewed]
Lets try it Ted. On commit I added in being able to set in config. an explicit
limit on how long balancer would run but that default is that this is not
specified. I also added logging (DEBUG) for when balancer is cutoff because it
ran out of time.
Thanks for the patch Ted. Committed to TRUNK.
> 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
> Fix For: 0.92.0
>
> 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
