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/05/28 23:07:00 UTC

[jira] [Created] (HBASE-24463) Allow operator to limit total normalization work per invocation

Nick Dimiduk created HBASE-24463:
------------------------------------

             Summary: 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
            Reporter: Nick Dimiduk


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)