[
https://issues.apache.org/jira/browse/HBASE-25513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269226#comment-17269226
]
Baiqiang Zhao commented on HBASE-25513:
---------------------------------------
Thanks [~ndimiduk]. Normalizer is a nice feature, and we backport this feature
to our production cluster. And in my view, there may be two points that can be
optimized: 1. Table can be enabled and disabled merge/split in TableDescriptor,
we should judge before calculating the plan 2. Part of the configuration can be
set by table level. For example, hbase.normalizer.min.region.count can be set
by "alter ‘table’, CONFIGURATION=>\{'hbase.normalizer.min.region.count' =>
'5'}". If the table is not set, then use the global configuration which is set
in hbase-site.xml. How do you feel?
> When the table is turned on normalize, the first region may not be merged
> even the size is 0
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-25513
> URL: https://issues.apache.org/jira/browse/HBASE-25513
> Project: HBase
> Issue Type: Bug
> Components: Normalizer
> Affects Versions: 3.0.0-alpha-1, 2.4.1
> Reporter: Baiqiang Zhao
> Assignee: Baiqiang Zhao
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.2
>
>
> Suppose a table has 8 regions, the sizes are [0, 10, 1, 0, 9, 0, 12, 0], the
> average region size is 4, and split is disabled.
> The current Normalizer can only get three merge plans (use size to represent
> region):
> [1, 0], [9, 0],[12, 0]
> It can not merge the first region, even it's size is 0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
