Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # user - Region balancing question


Copy link to this message
-
RE: Region balancing question
Ramkrishna.S.Vasudevan 2012-08-02, 10:08
hbase.master.loadbalance.bytable - By default it is true.

Regards
Ram

> -----Original Message-----
> From: Anoop Sam John [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 02, 2012 3:32 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Region balancing question
>
> Seems this is available from 0.92 version..   See HBASE-3373
>
> -Anoop-
> ________________________________________
> From: Anoop Sam John [[EMAIL PROTECTED]]
> Sent: Thursday, August 02, 2012 3:24 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Region balancing question
>
> Hi
>   Which version you are using?
> From 0.94 in the balancer there are 2 ways of balancing. One is by
> table balancing in which balancer will make sure the regions for one
> table is balanced across the RSs. But in the other way of balancing in
> generic way it will consider all the regions across all the tables as
> one group only and will balance all across the RSs.  Seems the 2nd way
> is happening with ur case. Can u check the total number of regions
> (across all the tables) in every RS. Is this balanced now?
>
> "hbase.master.loadbalance.bytable" config param can select any of the 2
> ways of balancing. This is added in 0.94 version. You might be using
> some older version?
>
> -Anoop-
> ________________________________________
> From: Bryan Keller [[EMAIL PROTECTED]]
> Sent: Thursday, August 02, 2012 11:37 AM
> To: [EMAIL PROTECTED]
> Subject: Region balancing question
>
> I have a table on a 4 node test cluster. I also have some other tables
> on the cluster. The table in question has a total of 12 regions. I
> noticed that 1 node has 6 regions, another has zero, and the remaining
> two nodes have the expected 3 regions. I'm a little confused how this
> can happen.
>
> The node with zero regions for the table has regions for other tables,
> so the node seems to be functioning properly. I'm not sure how this
> particular table can end up having no regions on this one node. Should
> the balancer distribute the regions evenly across the cluster for a
> given table? If so, is there a way to force it to rebalance?