You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/05/28 23:17:00 UTC

[jira] [Created] (HBASE-24464) Normalizer should have configuration for minimum region size

Nick Dimiduk created HBASE-24464:
------------------------------------

             Summary: Normalizer should have configuration for minimum region size
                 Key: HBASE-24464
                 URL: https://issues.apache.org/jira/browse/HBASE-24464
             Project: HBase
          Issue Type: Improvement
          Components: master
            Reporter: Nick Dimiduk


Another issue raised in PR review on HBASE-24418. With the current implementation, the lower-bound on how small the normalizer will make a region is its lowest granularity of size measurement: 1mb. That means it will happily balance a table out to be 1000 * 1mb regions (probably not likely, but seems plausible). The proposal was to add configuration knob that specifies the lower bound on region size as a guard against excessive splitting, something of an analogue to {{hbase.hregion.max.filesize}}.

I'm not convinced this is really needed; I think the table would need to have been crafted intentionally to trigger this behavior. However, it seems like a reasonable guard rail to install. Discuss.



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