You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2022/11/18 18:32:00 UTC

[jira] [Resolved] (HBASE-27399) Add config for setting a max actions per normalizer run

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

Bryan Beaudreault resolved HBASE-27399.
---------------------------------------
    Resolution: Duplicate

> Add config for setting a max actions per normalizer run
> -------------------------------------------------------
>
>                 Key: HBASE-27399
>                 URL: https://issues.apache.org/jira/browse/HBASE-27399
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Bryan Beaudreault
>            Priority: Major
>
> When you enable the normalizer for the first time on an existing table, the next time it runs it can do a massive amount of merges/splits. This can be painful for callers.
> Additionally, if someone were to write a large amount of Puts or Deletes it may cause a merge/split storm as well.
> We should add a config which allows operators to limit the amount of actions per run. This way the normalizer can work towards its plan gracefully over the course of a few hours rather than all at once.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)