hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8432) a table with unbalanced regions will balance indefinitely with the 'org.apache.hadoop.hbase.master.DefaultLoadBalancer'
Date Fri, 19 Jul 2013 04:21:07 GMT

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

Hadoop QA commented on HBASE-8432:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12593115/8432-trunk.txt
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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:red}-1 site{color}.  The patch appears to cause mvn site goal to fail.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/6405//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6405//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6405//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6405//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6405//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6405//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6405//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6405//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6405//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/6405//console

This message is automatically generated.
                
> a table with unbalanced regions will balance indefinitely with the 'org.apache.hadoop.hbase.master.DefaultLoadBalancer'
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8432
>                 URL: https://issues.apache.org/jira/browse/HBASE-8432
>             Project: HBase
>          Issue Type: Bug
>          Components: Balancer
>    Affects Versions: 0.94.5
>         Environment: Linux 2.6.32-el5.x86_64
>            Reporter: Wang Qiang
>              Labels: patch
>             Fix For: 0.98.0, 0.95.2, 0.94.10
>
>         Attachments: 8432-0.94.txt, 8432-trunk.txt, patch_20130716.txt
>
>
> it happened that a table with unbalanced regions, as follows in my cluster(the cluster
has 20 regionservers, the table has 12 regions):
> http://hadoopdev19.cm6:60030/	1
> http://hadoopdev8.cm6:60030/	2
> http://hadoopdev17.cm6:60030/	1
> http://hadoopdev12.cm6:60030/	1
> http://hadoopdev5.cm6:60030/	1
> http://hadoopdev9.cm6:60030/	1
> http://hadoopdev22.cm6:60030/	1
> http://hadoopdev11.cm6:60030/	1
> http://hadoopdev21.cm6:60030/	1
> http://hadoopdev16.cm6:60030/	1
> http://hadoopdev10.cm6:60030/	1
> with the 'org.apache.hadoop.hbase.master.DefaultLoadBalancer', after 5 times load-balances,
the table are still unbalanced:
> http://hadoopdev3.cm6:60030/	1
> http://hadoopdev20.cm6:60030/	1
> http://hadoopdev4.cm6:60030/	2
> http://hadoopdev18.cm6:60030/	1
> http://hadoopdev12.cm6:60030/	1
> http://hadoopdev14.cm6:60030/	1
> http://hadoopdev15.cm6:60030/	1
> http://hadoopdev6.cm6:60030/	1
> http://hadoopdev13.cm6:60030/	1
> http://hadoopdev11.cm6:60030/	1
> http://hadoopdev10.cm6:60030/	1
> http://hadoopdev19.cm6:60030/	1
> http://hadoopdev17.cm6:60030/	1
> http://hadoopdev8.cm6:60030/	1
> http://hadoopdev5.cm6:60030/	1
> http://hadoopdev12.cm6:60030/	1
> http://hadoopdev22.cm6:60030/	1
> http://hadoopdev11.cm6:60030/	1
> http://hadoopdev21.cm6:60030/	1
> http://hadoopdev7.cm6:60030/	2
> http://hadoopdev10.cm6:60030/	1
> http://hadoopdev16.cm6:60030/	1
> http://hadoopdev3.cm6:60030/	1
> http://hadoopdev20.cm6:60030/	1
> http://hadoopdev4.cm6:60030/	1
> http://hadoopdev18.cm6:60030/	2
> http://hadoopdev12.cm6:60030/	1
> http://hadoopdev14.cm6:60030/	1
> http://hadoopdev15.cm6:60030/	1
> http://hadoopdev6.cm6:60030/	1
> http://hadoopdev13.cm6:60030/	1
> http://hadoopdev11.cm6:60030/	1
> http://hadoopdev10.cm6:60030/	1
> http://hadoopdev19.cm6:60030/	1
> http://hadoopdev8.cm6:60030/	1
> http://hadoopdev17.cm6:60030/	1
> http://hadoopdev12.cm6:60030/	1
> http://hadoopdev5.cm6:60030/	1
> http://hadoopdev22.cm6:60030/	1
> http://hadoopdev11.cm6:60030/	1
> http://hadoopdev7.cm6:60030/	1
> http://hadoopdev21.cm6:60030/	2
> http://hadoopdev16.cm6:60030/	1
> http://hadoopdev10.cm6:60030/	1
> http://hadoopdev3.cm6:60030/	1
> http://hadoopdev20.cm6:60030/	1
> http://hadoopdev18.cm6:60030/	1
> http://hadoopdev4.cm6:60030/	1
> http://hadoopdev12.cm6:60030/	1
> http://hadoopdev15.cm6:60030/	1
> http://hadoopdev14.cm6:60030/	2
> http://hadoopdev6.cm6:60030/	1
> http://hadoopdev13.cm6:60030/	1
> http://hadoopdev11.cm6:60030/	1
> http://hadoopdev10.cm6:60030/	1
> from the above logs, we can also find that some regions needn't move, but they moved.
follow into 'org.apache.hadoop.hbase.master.DefaultLoadBalancer.balanceCluster()', I found
that 'maxToTake' is error calculated. 

--
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