[
https://issues.apache.org/jira/browse/HBASE-22285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868961#comment-16868961
]
Andrew Purtell commented on HBASE-22285:
----------------------------------------
I do think it is valid to disable normalization temporarily when warming up on
a pre split table. For that I do think you can use the age of the table as a
guide. Don't begin normalizing it until it is one day old, some threshold like
that. Make it configurable. Simple. One day as default should be sufficient to
keep the normalizer from getting in the way of someone loading their table for
testing. If they want finer control than this they could disable it.
> A normalizer which merges very small size regions with adjacent
> regions.(MergeToNormalize)
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-22285
> URL: https://issues.apache.org/jira/browse/HBASE-22285
> Project: HBase
> Issue Type: New Feature
> Components: regionserver
> Reporter: Aman Poonia
> Assignee: Aman Poonia
> Priority: Minor
>
> There are scenarios where we have seen around 5% of total regions with a size
> of 0 bytes and another 5-6 % regions with size in a few bytes. These kinds of
> regions increase with time considering we have TTL over the rows.
> After exploring the option of RegionNormalizer and doing some quick runs we
> found that that is not suitable considering it also splits the regions and
> merges to normalize. What we really want is to split as per Split policy and
> merge very small regions with adjacent regions to make sure we reduce 0-byte
> regions.
> We can plugin this normalizer using the property
> "hbase.master.normalizer.class"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
