You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/06/12 15:30:00 UTC
[jira] [Updated] (HBASE-28658) The failsafe snapshot should be deleted after rollback successfully
[ https://issues.apache.org/jira/browse/HBASE-28658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HBASE-28658:
-----------------------------------
Labels: pull-request-available (was: )
> The failsafe snapshot should be deleted after rollback successfully
> -------------------------------------------------------------------
>
> Key: HBASE-28658
> URL: https://issues.apache.org/jira/browse/HBASE-28658
> Project: HBase
> Issue Type: Bug
> Components: Client, snapshots
> Affects Versions: 2.4.13
> Reporter: guluo
> Assignee: guluo
> Priority: Major
> Labels: pull-request-available
>
> When a table exists and is in a disabled state, hbase supports to restore by the snapshot of this table.
> In this scenario, hbase would create a failsafe snapshot for this disabled table, and hbase would rollback by this failsafe snapshot when fail to restore.
> However on hbase cluster, the failsafe snapshot still exists after rollback successfully by failsafe snapshot.
> I think when restore failed by table snapshot but rollback successfully by failsafe snapshot, this failsafe snapshot should be deleted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)