[ https://issues.apache.org/jira/browse/HBASE-19021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206963#comment-16206963 ]
Jerry He commented on HBASE-19021: ---------------------------------- bq. Why the negation ? {code} * @param forceByCluster a flag to force to aggregate the server-load to the cluster level * @return A clone of current assignments by table. */ public Map<TableName, Map<ServerName, List<RegionInfo>>> getAssignmentsByTable( final boolean forceByCluster) { if (!forceByCluster) return getAssignmentsByTable(); {code} !isByTable will be cluster level. > Restore a few important missing logics for balancer in 2.0 > ---------------------------------------------------------- > > Key: HBASE-19021 > URL: https://issues.apache.org/jira/browse/HBASE-19021 > Project: HBase > Issue Type: Bug > Reporter: Jerry He > Assignee: Jerry He > Priority: Critical > > After looking at the code, and some testing, I see the following things are > missing for balancer to work properly after AMv2. > # hbase.master.loadbalance.bytable is not respected. It is always 'bytable'. > Previous default is cluster wide, not by table. > # Servers with no assignments is not added for balance consideration. > # Crashed server is not removed from the in-memory server map in > RegionStates, which affects balance. > # Draining marker is not respected when balance. > Also try to re-enable {{TestRegionRebalancing}}, which has a > {{testRebalanceOnRegionServerNumberChange}} -- This message was sent by Atlassian JIRA (v6.4.14#64029)