Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A6AA810AB9 for ; Tue, 16 Jul 2013 09:42:54 +0000 (UTC) Received: (qmail 92324 invoked by uid 500); 16 Jul 2013 09:42:52 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 92236 invoked by uid 500); 16 Jul 2013 09:42:51 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 92195 invoked by uid 99); 16 Jul 2013 09:42:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jul 2013 09:42:50 +0000 Date: Tue, 16 Jul 2013 09:42:50 +0000 (UTC) From: "Wang Qiang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8432) a table with unbalanced regions will balance indefinitely with the 'org.apache.hadoop.hbase.master.DefaultLoadBalancer' MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709646#comment-13709646 ] Wang Qiang commented on HBASE-8432: ----------------------------------- [~jmspaggi] yes, I have tested all the 3 different scenarios in our cluster > 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 > Priority: Critical > Attachments: 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