[
https://issues.apache.org/jira/browse/HBASE-28215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault resolved HBASE-28215.
---------------------------------------
Fix Version/s: 2.6.0
3.0.0-beta-1
Release Note:
Adds new configurations to control the speed and batching of region reopens
after modifying a table:
- hbase.reopen.table.regions.progressive.batch.size.max - When set, the HMaster
will progressively reopen regions, starting with one region and then doubling
until it reaches the specified max. After reaching the max, it will continue
reopening at that batch size until all regions are reopened.
- hbase.reopen.table.regions.progressive.batch.backoff.ms - When set, the
HMaster will back off for this amount of time between each batch.
Resolution: Fixed
Pushed to master, branch-3, branch-2, branch-2.6
Thanks for the contribution [~rmdmattingly]!
> Region reopen procedure should support some sort of throttling
> --------------------------------------------------------------
>
> Key: HBASE-28215
> URL: https://issues.apache.org/jira/browse/HBASE-28215
> Project: HBase
> Issue Type: Improvement
> Components: master, proc-v2
> Reporter: Ray Mattingly
> Assignee: Ray Mattingly
> Priority: Major
> Fix For: 2.6.0, 3.0.0-beta-1
>
>
> The mass reopening of regions caused by a table descriptor modification can
> be quite disruptive. For latency/error sensitive workloads, like our user
> facing traffic, we need to be very careful about when we modify table
> descriptors, and it can be virtually impossible to do it painlessly for busy
> tables.
> It would be nice if we supported configurable batching/throttling of
> reopenings so that the amplitude of any disruption can be kept relatively
> small.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
