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/11/04 03:40:00 UTC
[jira] [Updated] (HBASE-26370) Unexpected crash fails the truncate
operation and 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:
------------------------------
Description:
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 assigns 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.
In HMaster2, we got following info:
{code:java}
INFO [ProcedureExecutor-12] procedure2.ProcedureExecutor: Rolledback procedure TruncateTableProcedure (table=mytable preserveSplits=true) id=9 owner=myhbase state=ROLLEDBACK exec-time=4.6030 sec exception=org.apache.hadoop.hbase.TableNotDisabledException: mytable
{code}
was:
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.
In HMaster2, we got following info:
{code:java}
INFO [ProcedureExecutor-12] procedure2.ProcedureExecutor: Rolledback procedure TruncateTableProcedure (table=mytable preserveSplits=true) id=9 owner=myhbase state=ROLLEDBACK exec-time=4.6030 sec exception=org.apache.hadoop.hbase.TableNotDisabledException: mytable
{code}
> Unexpected crash fails the truncate operation and 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 assigns 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.
> In HMaster2, we got following info:
> {code:java}
> INFO [ProcedureExecutor-12] procedure2.ProcedureExecutor: Rolledback procedure TruncateTableProcedure (table=mytable preserveSplits=true) id=9 owner=myhbase state=ROLLEDBACK exec-time=4.6030 sec exception=org.apache.hadoop.hbase.TableNotDisabledException: mytable
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)