[
https://issues.apache.org/jira/browse/HBASE-10127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845584#comment-13845584
]
Elliott Clark commented on HBASE-10127:
---------------------------------------
It still is using the AM.getAssignmentsByTable() and then passing only one
table's worth of assignments if that table name matches. That function depends
on hbase.master.loadbalance.bytable's value and will give different results
based on if it's turned on or off.
In trunk this won't work at all (by table is turned off). In 0.94 this won't
work when hbase.master.loadbalance.bytable is false.
By table balancing is there only because the balancer hasn't done it's job
well. All things that by table balancing handled should be fixed in 0.96 and
forward.
> 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
(v6.1.4#6159)
