[
https://issues.apache.org/jira/browse/HBASE-25549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769927#comment-17769927
]
Gourab Taparia commented on HBASE-25549:
----------------------------------------
[~GeorryHuang] Agree on the fact that we should not allow adding/removing
Column families and even changing replicas. Can we allow modifying CF
properties though ?
Given that without this mode, there will be a RIT storm when applying the CF
property change. With this option, even though the state can be in-consistent
all the regions have re-opened, we give the onus to the end user if they want
to use this for CF property change or it. We are also already displaying a
warning regarding the same. For e.g. I have a use case to modify CF TTL
property on existing table, and am fine with TTL being inconsistent till its
applied to all.
I am fine with either, just reaching out if its better to allow modifying the
properties too here.
> 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)
