[
https://issues.apache.org/jira/browse/HBASE-22285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868960#comment-16868960
]
Andrew Purtell commented on HBASE-22285:
----------------------------------------
bq. Is it possible to add this functionality to existing Normalizer
implementations?
With the existing normalizer you could add a configuration option that toggles
on/off whether or not the RegionNormalizer will do a split. Turn it off, then
you get the intent here, merge only.
Or you could turn off merging, then the normalizer only does splitting. Less
useful, arguably, but consistent in principle.
> 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)
