You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/08/04 01:10:00 UTC
[jira] [Work started] (HBASE-24628) Normalizer needs a throttle
[ https://issues.apache.org/jira/browse/HBASE-24628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HBASE-24628 started by Nick Dimiduk.
--------------------------------------------
> Normalizer needs a throttle
> ---------------------------
>
> Key: HBASE-24628
> URL: https://issues.apache.org/jira/browse/HBASE-24628
> Project: HBase
> Issue Type: Improvement
> Components: Normalizer
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
>
> There's no limits on the normalizer right now. It will iterate through the tables one at a time until it's touched all tables. For any table, it generates a complete plan and executes that plan in totality.
> It would be nice to allow operators to configure some limits here. Off the top of my head, the two metrics that might be interesting are {{split|merge actions / hour}} or {{hfile mb volume / hour}}. Either way, we'd need to track a little more metadata.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)