[
https://issues.apache.org/jira/browse/HBASE-25549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769099#comment-17769099
]
Zhuoyue Huang commented on HBASE-25549:
---------------------------------------
I've made some adjustments for this issue:
1. Remove the concept of "lazy mode," as I believe it could confuse developers.
So, I've replaced all instances of the boolean variable "lazy_mode" in my code
with "reopenRegions," which is more straightforward.
2. By default, any table modification operation will set "reopenRegions" to
true.
3. If you modify a table using a shell command like "alter 't1',
METHOD=>'no_reopen_regions'," "reopenRegions" will be set to false, and the
table modification operation will not reopen any regions.
4. I've changed the title of this issue from "Provide lazy mode when modifying
table to avoid RIT storm" to "Provide a switch that allows avoiding reopening
all regions when modifying a table to prevent RIT storms"
> Provide a switch that allows avoiding reopening all regions when modifying a
> table to prevent RIT storms.
> ---------------------------------------------------------------------------------------------------------
>
> Key: HBASE-25549
> URL: https://issues.apache.org/jira/browse/HBASE-25549
> Project: HBase
> Issue Type: Improvement
> Components: master, shell
> Affects Versions: 3.0.0-alpha-1
> Reporter: Zhuoyue Huang
> Assignee: Zhuoyue Huang
> Priority: Major
> Fix For: 2.6.0, 2.5.6, 3.0.0-beta-1
>
>
> Under normal circumstances, modifying a table will cause all regions
> belonging to the table to enter RIT. Imagine the following two scenarios：
> # Someone entered the wrong configuration （e.g. negative
> 'hbase.busy.wait.multiplier.max' value） when altering the table, causing
> thousands of online regions to fail to open, leading to online accidents.
> # Modify the configuration of a table, but this modification is not urgent,
> the regions are not expected to enter RIT immediately.
> -'alter_lazy' is a new command to modify a table without reopening any online
> regions except those regions were assigned by other threads or split etc.-
>
> Provide an optional lazy_mode for the alter command to modify the
> TableDescriptor without the region entering the RIT. The modification will
> take effect when the region is reopened.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
