Details
Description
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:
Admin#reshapeTable(TableName, int numSplits);
or from the shell:
> reshape TABLE, numSplits
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.
Attachments
Attachments
Issue Links
- is related to
-
HBASE-14838 Clarify that SimpleRegionNormalizer does not merge empty (<1MB) regions
- Closed
-
HBASE-13964 Skip region normalization for tables under namespace quota
- Closed
-
HBASE-15073 Finer grained control over normalization actions for RegionNormalizer
- Closed
- relates to
-
HBASE-15098 Normalizer switch in configuration is not used
- Closed
-
HBASE-14367 Add normalization support to shell
- Closed
-
HBASE-15124 Document the new 'normalization' feature in refguid
- Closed
- supercedes
-
HBASE-7629 Master initiated automatic region merges
- Closed
-
HBASE-3521 region be merged with others automatically when all data in the region has expired and removed, or region gets too small.
- Closed
- links to