[
https://issues.apache.org/jira/browse/HBASE-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628717#comment-13628717
]
Hadoop QA commented on HBASE-8119:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12578136/hbase-8119_v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified tests.
{color:red}-1 hadoop2.0{color}. The patch failed to compile against the
hadoop 2.0 profile.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5257//console
This message is automatically generated.
> Optimize StochasticLoadBalancer
> -------------------------------
>
> 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
> Assignee: Enis Soztutar
> Priority: Critical
> Fix For: 0.95.1
>
> Attachments: hbase-8119_v2.patch
>
>
> 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
