[ https://issues.apache.org/jira/browse/HBASE-24628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang resolved HBASE-24628. ------------------------------- Hadoop Flags: Reviewed Resolution: Fixed The flaky board is back to normal. Resolve. > Region normalizer now respects a rate limit > ------------------------------------------- > > 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 > Fix For: 3.0.0-alpha-1, 2.4.0 > > > 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)