You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "anonymous (Jira)" <ji...@apache.org> on 2021/10/19 10:40:00 UTC

[jira] [Updated] (HBASE-26370) Unexpected crash makes a disabled table enabled

     [ https://issues.apache.org/jira/browse/HBASE-26370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

anonymous updated HBASE-26370:
------------------------------
    Summary: Unexpected crash makes a disabled table enabled  (was: Unexpected crash makes a disabled table be enabled)

> Unexpected crash makes a disabled table enabled
> -----------------------------------------------
>
>                 Key: HBASE-26370
>                 URL: https://issues.apache.org/jira/browse/HBASE-26370
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.7.1
>            Reporter: anonymous
>            Priority: Major
>
> There is a tableĀ {{mytable}} in a HBase cluster with two HMasters and two RegionServers.
> 1. Current active HMaster is HMaster1;
> 2. Client disabled the table {{mytable}};
> 3. {{mytable}} is in disabled state;
> 4. Client request to truncate {{mytable}};
> 5. HMaster1 tries to truncate {{mytable}}. For the TruncateTableState {{TRUNCATE_TABLE_ASSIGN_REGIONS}}, HMaster1 tries to assign regions of the table and mark the table as Enabling;
> 6. HMaster1 crashes;
> 7. HMaster2 becomes active;
> 8. The truncate operation fails due to {{TableNotDisabledException}}, and {{mytable}} was left as enabled.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)