You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2021/04/07 20:26:00 UTC
[jira] [Updated] (HBASE-25744) Change default of
`hbase.normalizer.merge.min_region_size.mb` to `0`
[ https://issues.apache.org/jira/browse/HBASE-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk updated HBASE-25744:
---------------------------------
Release Note: Before this change, by default, the normalizer would exclude any region with a total `storefileSizeMB` <= 1 from merge consideration. This changes the default so that these small regions will be merged away.
> Change default of `hbase.normalizer.merge.min_region_size.mb` to `0`
> --------------------------------------------------------------------
>
> Key: HBASE-25744
> URL: https://issues.apache.org/jira/browse/HBASE-25744
> Project: HBase
> Issue Type: Improvement
> Components: master, Normalizer
> Affects Versions: 3.0.0-alpha-1, 2.5.0
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
>
> The current default value is {{1}}, which means normalizer will leave regions of 0-1mb size hanging around. We should set this down to {{0}} so that these small regions go away by default. As I recall, the value was set as it is in order to prevent the normalizer from merging up regions immediately after an operator creates a pre-split table. IMHO, this use case is more than covered by these other configurations with their default values:
> * {{hbase.normalizer.min.region.count=3}}
> * {{hbase.normalizer.merge.min_region_age.days=3}}
> For details, see
> * http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/master/normalizer/package-summary.html#package.description
> * http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/master/normalizer/SimpleRegionNormalizer.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)