[
https://issues.apache.org/jira/browse/HBASE-24463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24463.
----------------------------------
Resolution: Won't Fix
The ability to limit the normalizer is now provided by rate limiting.
> Allow operator to limit total normalization work per invocation
> ---------------------------------------------------------------
>
> Key: HBASE-24463
> URL: https://issues.apache.org/jira/browse/HBASE-24463
> Project: HBase
> Issue Type: Improvement
> Components: master, Normalizer
> Reporter: Nick Dimiduk
> Priority: Major
>
> During review on HBASE-24418, we observed that there's no way for an operator
> to limit the total amount of work a normalizer invocation will do. One
> suggestion was allowing settings for maximum number of plan executions per
> table or maximum number of plan executions per run. I've seen other systems
> limit the amount of CPU time permitted for a given run.
> At least we have a run lock that prevents multiple invocations from running
> concurrently, which should prevent one run from starting before the previous
> one finished.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
