hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10127) support balance table
Date Thu, 12 Dec 2013 19:32:08 GMT

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

Elliott Clark commented on HBASE-10127:

bq.Elliott Clark, are you saying that trunk should get this patch or this functionality?
* I think that it shouldn't need it.  It has an idea of spreading the one table to lots of
region servers.
* Additionally the balancer in 96+ will fight with itself if we balance by table only and
then balance the whole cluster.
* Lastly I think that the getAssignmentByTable function is an abomination, and should be removed.
 I would prefer to move things off that function and not onto it.
** Deciding to balance by table or in total should be something the balancer does, it shouldn't
be part of the AM that's grouping by table name.
** Having the function return something completely different than the name suggests because
of a config is just hacky.

bq.For 0.94 this is a simple patch. I'd +1 for that part. 
It will be broken for anyone with by table balancing turned off though (People with lots of
tables might have turned this off as it can result in a really bad balance).  Seems weird
to have a command that will run but not work depending upon the settings.

> support balance table
> ---------------------
>                 Key: HBASE-10127
>                 URL: https://issues.apache.org/jira/browse/HBASE-10127
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, shell
>    Affects Versions: 0.94.14
>            Reporter: cuijianwei
>         Attachments: HBASE-10127-0.94-v1.patch
> HMaster provides a rpc interface : 'balance()' to balance all the regions among region
servers in the cluster. Sometimes, we might want to balance all the regions belonging to a
table while keeping the region assignments of other tables. This demand may reveal in a shared
cluster where we want to balance regions for one application's table without affecting other
applications. Therefore, will it be useful if we extend the current 'balance()' interface
to only balance regions of the same table? 

This message was sent by Atlassian JIRA

View raw message