[
https://issues.apache.org/jira/browse/HBASE-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030352#comment-13030352
]
Ted Yu commented on HBASE-3866:
-------------------------------
Currently Master supports "hbase.balancer.max.balancing" which is the maximum
time (in milliseconds) each balance() call can take. If
"hbase.balancer.max.balancing" isn't specified, half of "hbase.balancer.period"
is used (2.5 minutes by default).
If the slow movement applies to all regions moved (not just regions moved onto
empty region servers), you can set "hbase.balancer.max.balancing" short.
Another enhancement is to introduce "hbase.balancer.max.regions.periteration"
which controls the maximum number of regions that are moved per balance() call.
> Script to add regions gradually to a new regionserver.
> ------------------------------------------------------
>
> Key: HBASE-3866
> URL: https://issues.apache.org/jira/browse/HBASE-3866
> Project: HBase
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 0.90.2
> Reporter: Aravind Gottipati
> Priority: Minor
> Attachments: slow_balancer.rb, slow_balancer.rb
>
>
> When a new region server is brought online, the current balancer kicks off a
> whole bunch of region moves and causes a lot of regions to be un-available
> right away. A slower balancer that gradually balances the cluster is
> probably a good script to have. I have an initial version that mooches off
> the region_mover script to do this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
