You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2023/12/01 20:10:00 UTC

[jira] [Commented] (HBASE-25549) Provide a switch that allows avoiding reopening all regions when modifying a table to prevent RIT storms.

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

Bryan Beaudreault commented on HBASE-25549:
-------------------------------------------

Backport has been pushed to branch-2, branch-2.6, and branch-2.5. Thanks [~gourab.taparia] for the contribution!

FYI the original master commit had been missed backporting to branch-3, so I took care of that.

Thanks to [~GeorryHuang] for the work here, and everyone else for the interest, input, and reviews! It was nice to see such an active thread of discussion and contribution on this one, sort of reminiscent of the old days :) 

> 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, 3.0.0-beta-1, 2.5.7
>
>
> 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)