Right, that's config. You can turn it on and restart the cluster.
Upstream it is on by default. However, it is turned off by default in
CDH4.1.2 to be backward compatible.
On Tue, Dec 4, 2012 at 11:28 AM, Norbert Burger
<[EMAIL PROTECTED]> wrote:
> Thanks, Jimmy. Do you mean the config
> "hbase.master.loadbalance.bytable"? According to  and , it is
> "true" by default.
>  https://issues.apache.org/jira/secure/attachment/12509174/3373.txt
>  http://search-hadoop.com/m/M6z7G1PKejw
> On Tue, Dec 4, 2012 at 2:23 PM, Jimmy Xiang <[EMAIL PROTECTED]> wrote:
>> In CDH4.1.2, per table region balancing is turned off by default.
>> You can change the configuration to turn it on.
>> On Tue, Dec 4, 2012 at 11:10 AM, Ted Yu <[EMAIL PROTECTED]> wrote:
>>> Can you give us a little more detail on how much deviation the region
>>> counts on region servers have ?
>>> There is a parameter, hbase.regions.slop, with default value of 0.2
>>> This parameter allows region count to deviate by certain percentage from
>>> average region count.
>>> You can tighten the value for this parameter and see if you get better
>>> I will also put the above summary on HBASE-3373.
>>> On Tue, Dec 4, 2012 at 8:42 AM, Norbert Burger <[EMAIL PROTECTED]>wrote:
>>>> We upgraded to CDH4.1.2 (contains HBASE-3373) in one of our
>>>> environments. After filling that environment with data, I was
>>>> surprised to see that regions were not balanced across regionservers
>>>> at the table level. We have restarted all regionservers at least once
>>>> In , I see Stack's reference to temporarily adding
>>>> "hbase.master.startup.retainassign=false" and restarting nodes. Is
>>>> this a necessary step on the path to region balancing nirvana?
>>>>  http://search-hadoop.com/m/MQSPEyUQIv1