[jira] [Commented] (HBASE-28215) Region reopen procedure should support some sort of throttling

["Hudson (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-28215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839838#comment-17839838 ] 

Hudson commented on HBASE-28215:
--------------------------------

Results for branch master
	[build #1058 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1058/]: (/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1058/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1058/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1058/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> 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)