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

Nick Dimiduk updated HBASE-24628:
---------------------------------
    Release Note: 
<!-- markdown -->
Introduces a new configuration, 
`hbase.normalizer.throughput.max_bytes_per_sec`, for specifying a limit on the 
throughput of actions executed by the normalizer. Note that while this 
configuration value is in bytes, the minimum honored valued is `1,000,000`, or 
`1m`. Supports values configured using the human-readable suffixes honored by 
[`Configuration.getLongBytes`](https://hadoop.apache.org/docs/current/api/org/apache/hadoop/conf/Configuration.html#getLongBytes-java.lang.String-long-)

  was:
<!-- markdown -->
Introduces a new configuration, 
`hbase.normalizer.throughput.max_bytes_per_sec`, for specifying a
limit on the throughput of actions executed by the normalizer. Note
that while this configuration value is in bytes, the minimum honored
valued is `1,000,000`, or `1m`. Supports values configured using the
human-readable suffixes honored by 
[`Configuration.getLongBytes`](https://hadoop.apache.org/docs/current/api/org/apache/hadoop/conf/Configuration.html#getLongBytes-java.lang.String-long-)


> Normalizer needs a throttle
> ---------------------------
>
>                 Key: HBASE-24628
>                 URL: https://issues.apache.org/jira/browse/HBASE-24628
>             Project: HBase
>          Issue Type: Improvement
>          Components: Normalizer
>    Affects Versions: 3.0.0-alpha-1, 2.4.0
>            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)

Reply via email to