You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Aman Poonia (Jira)" <ji...@apache.org> on 2021/07/08 06:05:00 UTC

[jira] [Created] (HBASE-26073) Avoid merging regions if tables has not reached the state where numbers of regions are not split because of number of regions

Aman Poonia created HBASE-26073:
-----------------------------------

             Summary: Avoid merging regions if tables has not reached the state where numbers of 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: 2.4.4, 1.7.0
            Reporter: Aman Poonia
            Assignee: Aman Poonia


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 regions in creating plans for normalizer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)