[
https://issues.apache.org/jira/browse/HBASE-13103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343658#comment-14343658
]
Nick Dimiduk commented on HBASE-13103:
--------------------------------------
I'd like to see the cluster make iterative attempts toward an ideal state, not
require users to track this stuff manually.
Just like we have a balancer chore in master that aims to keep assignment
healthy, we could have a split/merge chore that tries the same. Would need some
way to decide if a region is "hot" or not, but I think a simple bit of
conservative logic might look like "region is 50% smaller than average or 50%
larger than average and hasn't served writes in the last hour".
> [ergonomics] add shell,API to "reshape" a table
> -----------------------------------------------
>
> Key: HBASE-13103
> URL: https://issues.apache.org/jira/browse/HBASE-13103
> Project: HBase
> Issue Type: Brainstorming
> Components: Usability
> Reporter: Nick Dimiduk
>
> 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}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
