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

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

After I deleted other 5 tables, which span ~175 regions, StochasticLoadBalancer 
was able to run in 26 sec, and after that regions are balanced. 
{code}
2013-03-15 03:05:41,943 DEBUG 
org.apache.hadoop.hbase.master.balancer.StochasticLoadBalancer: Finished 
computing new laod balance plan.  Computation took 26904ms to try 15000 
different iterations.  Found a solution that moves 196 regions; Going from a 
computed cost of 65.70466155810982 to a new cost of 14.744572158365262
{code}

{code}
server1         Fri Mar 15 03:02:12 UTC 2013    16041.0         52
server2         Fri Mar 15 03:02:12 UTC 2013    15785.0         52
server3         Fri Mar 15 03:02:13 UTC 2013    16667.0         52
server4         Fri Mar 15 03:02:13 UTC 2013    21632.0         53
server5         Fri Mar 15 03:02:13 UTC 2013    16974.0         52
Total:5                 87099   261
{code}
                
> 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

Reply via email to