[ https://issues.apache.org/jira/browse/HBASE-25549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17279457#comment-17279457 ]
Zhuoyue Huang commented on HBASE-25549: --------------------------------------- bq. I still have some doubts about any potential impact of this feature when altering properties such as codecs, replication or adding a new CF and the mis-use of a feature like this could cause. Will add more tests to make sure it's correct. [~esteban] > A new hbase shell command: 'alter_lazy' > --------------------------------------- > > 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: 3.0.0-alpha-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. -- This message was sent by Atlassian Jira (v8.3.4#803005)