[ https://issues.apache.org/jira/browse/HBASE-13103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390744#comment-14390744 ]
Mikhail Antonov commented on HBASE-13103: ----------------------------------------- Since that's the draft, many obviously needed things are missing, namely: - being able to choose which table to normalize - need to define normalization rules more strictly (including priority of operations? if table has both types of outlier in the ranks of its regions - too small and too big regions, then what action is more urgent) - run normalization across several tables in parallel - is that something we should/shouldn't do - detecting currently running merges and splits. Current simple rules are just that we don't touch system tables and tables with less than 3 regions. > [ergonomics] add region size balancing as a feature of master > ------------------------------------------------------------- > > Key: HBASE-13103 > URL: https://issues.apache.org/jira/browse/HBASE-13103 > Project: HBase > Issue Type: Brainstorming > Components: Usability > Reporter: Nick Dimiduk > Assignee: Mikhail Antonov > Attachments: HBASE-13103-v0.patch > > > Often enough, folks miss-judge split points or otherwise end up with a > suboptimal number of regions. We should have an automated, reliable way to > "reshape" or "balance" a table's region boundaries. This would be for tables > that contain existing data. This might look like: > {noformat} > Admin#reshapeTable(TableName, int numSplits); > {noformat} > or from the shell: > {noformat} > > reshape TABLE, numSplits > {noformat} > Better still would be to have a maintenance process, similar to the existing > Balancer that runs AssignmentManager on an interval, to run the above > "reshape" operation on an interval. That way, the cluster will automatically > self-correct toward a desirable state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)