hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6744) Per table balancing could cause regions unbalanced overall
Date Fri, 07 Sep 2012 21:42:08 GMT

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

stack commented on HBASE-6744:

+1 on making SLB default now.  Testing for 0.96.0 should shake out any bugs.  On its face
alone, it has a potential far in excess of the current, hard to untangle, served-us well up-to-this,
but needs-to-be retired now current balancer.
> Per table balancing could cause regions unbalanced overall
> ----------------------------------------------------------
>                 Key: HBASE-6744
>                 URL: https://issues.apache.org/jira/browse/HBASE-6744
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jimmy Xiang
> Per table balancing just balances regions based on tables.  However, overall, regions
could be seriously unbalanced.
> For example, if you shutdown all most all region serves in a cluster, then create tons
of new tables (no region pre-split), then start up all region servers.  You will see the regions
won't move to other region servers since they are balanced per table (only one region for
a table at this moment).
> If we can make the balance algorithm sophisticated enough, we don't need the configuration
hbase.master.loadbalance.bytable.  We can do the regular and bytable balancing at the same

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

View raw message