[
https://issues.apache.org/jira/browse/HBASE-22285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aman Poonia updated HBASE-22285:
--------------------------------
Description:
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"
was:
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 the normalizer using the property "hbase.master.normalizer.class"
> 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)
