[ https://issues.apache.org/jira/browse/HBASE-8517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665524#comment-13665524 ]
Hadoop QA commented on HBASE-8517: ---------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12584536/HBASE-8517-5.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 11 new or modified tests. {color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop 1.0 profile. {color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:green}+1 site{color}. The mvn site goal succeeds with this patch. {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/5799//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5799//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5799//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5799//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5799//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5799//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5799//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5799//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5799//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/5799//console This message is automatically generated. > Stochastic Loadbalancer isn't finding steady state on real clusters > ------------------------------------------------------------------- > > Key: HBASE-8517 > URL: https://issues.apache.org/jira/browse/HBASE-8517 > Project: HBase > Issue Type: Bug > Affects Versions: 0.95.0, 0.95.1 > Reporter: Elliott Clark > Assignee: Elliott Clark > Priority: Blocker > Fix For: 0.95.1 > > Attachments: HBASE-8517-0.patch, HBASE-8517-1.patch, > HBASE-8517-2.patch, HBASE-8517-3.patch, HBASE-8517-4.patch, HBASE-8517-5.patch > > > I have a cluster that runs IT tests. Last night after all tests were done I > noticed that the balancer was thrashing regions around. > The number of regions on each machine is not correct. > The balancer seems to value the cost of moving a region way too little. > {code} > 2013-05-09 16:34:58,920 DEBUG [IPC Server handler 4 on 60000] > org.apache.hadoop.hbase.master.balancer.StochasticLoadBalancer: Finished > computing new load balance plan. Computation took 5367ms to try 8910 > different iterations. Found a solution that moves 37 regions; Going from a > computed cost of 56.50254222730425 to a new cost of 11.214035466575254 > 2013-05-09 16:37:48,715 DEBUG [IPC Server handler 7 on 60000] > org.apache.hadoop.hbase.master.balancer.StochasticLoadBalancer: Finished > computing new load balance plan. Computation took 4735ms to try 8910 > different iterations. Found a solution that moves 38 regions; Going from a > computed cost of 56.612624531830996 to a new cost of 11.275763861636982 > 2013-05-09 16:38:11,398 DEBUG [IPC Server handler 6 on 60000] > org.apache.hadoop.hbase.master.balancer.StochasticLoadBalancer: Finished > computing new load balance plan. Computation took 4502ms to try 8910 > different iterations. Found a solution that moves 39 regions; Going from a > computed cost of 56.50048461413552 to a new cost of 11.225352339003237 > {code} > Each of those balancer runs were triggered when there was no load on the > cluster. -- 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