[
https://issues.apache.org/jira/browse/HBASE-26073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491804#comment-17491804
]
Aman Poonia edited comment on HBASE-26073 at 2/14/22, 5:45 AM:
---------------------------------------------------------------
[~ndimiduk] This is not an issue for us now as we use normalizer in a way that
we will not encounter this anymore.
To elaborate more, we configure min number of regions after which normalizer
should trigger to a number higher than number of region servers. In few cases
the number is as large as twice the number of RS in cluster.
was (Author: mnpoonia):
[~ndimiduk] This is not an issue for us now as we use normalizer in a way that
we will not encounter this anymore.
> Avoid merging regions if tables has not reached the state where regions are
> not split because of number of regions
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-26073
> URL: https://issues.apache.org/jira/browse/HBASE-26073
> Project: HBase
> Issue Type: Improvement
> Components: Normalizer
> Affects Versions: 1.7.0, 2.4.4
> Reporter: Aman Poonia
> Assignee: Aman Poonia
> Priority: Minor
>
> we have a table on a cluster with 100 regions with default split policy
> (SteppingSplitPolicy). This is a small table and will not get loaded with too
> much data. Now if region size of table is smaller than the normalizer target
> region size than there are chances that normalizer will consider the regions
> for merges. But since the number of regions are small split policy will
> trigger split on next flush. This is a continuous loop and our cluster will
> be busy in these two actions.
> We plan to consider number of regions and number of regionservers in creating
> plans for normalizer.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
