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

["Nick Dimiduk (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-24464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Dimiduk resolved HBASE-24464.
----------------------------------
    Resolution: Won't Fix

I don't think there's a strong case for this functionality. Reopen if you feel otherwise.

> 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, Normalizer
>            Reporter: Nick Dimiduk
>            Priority: Major
>
> 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)