You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Zhuoyue Huang (Jira)" <ji...@apache.org> on 2021/02/04 05:14:00 UTC
[jira] [Updated] (HBASE-25549) A new hbase shell command:
'alter_lazy'
[ https://issues.apache.org/jira/browse/HBASE-25549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhuoyue Huang updated HBASE-25549:
----------------------------------
Summary: A new hbase shell command: 'alter_lazy' (was: A new hbase shell command: 'lazy_alter')
> 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.
> 'lazy_alter' 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)