hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8119) StochasticLoadBalancer does not take into account per table balance
Date Fri, 15 Mar 2013 04:22:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603115#comment-13603115
] 

Enis Soztutar commented on HBASE-8119:
--------------------------------------

bq. yes this is by design. StochasticLoadbalancer went in with by table load balancing turned
off. Stochastic Balancer gets better results faster with by table load balancing turned off.
Yes, I think the title is misleading, will have to change it once I better understand whats
going on. 
I see two problems here 
 - the stochastic balancer takes 15min to compute even for this fairly simple cluster. Will
have to inspect why is this the case. 15000 iterations it not that much.
 - Once balancer creates the regionplans, they are not enforced it seems once the subsequent
invocation starts to run. 
                
> StochasticLoadBalancer does not take into account per table balance
> -------------------------------------------------------------------
>
>                 Key: HBASE-8119
>                 URL: https://issues.apache.org/jira/browse/HBASE-8119
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>    Affects Versions: 0.95.0
>            Reporter: Enis Soztutar
>             Fix For: 0.95.0
>
>
> On a 5 node trunk cluster, I ran into a weird problem with StochasticLoadBalancer:
> server1 	Thu Mar 14 03:42:50 UTC 2013 	0.0 	33
> server2 	Thu Mar 14 03:47:53 UTC 2013 	0.0 	34
> server3 	Thu Mar 14 03:46:53 UTC 2013 	465.0 	42
> server4 	Thu Mar 14 03:47:53 UTC 2013 	11455.0 	282
> server5 	Thu Mar 14 03:47:53 UTC 2013 	0.0 	34
> Total:5 		11920 	425
> Notice that server4 has 282 regions, while the others have much less. Plus for one table
with 260 regions has been super imbalanced:
> {code}
> Regions by Region Server
> Region Server	Region Count
> http://server3:60030/ 	10
> http://server4:60030/ 	250
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message