[
https://issues.apache.org/jira/browse/HBASE-30054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HBASE-30054:
-----------------------------------
Labels: pull-request-available (was: )
> Deleting a FAILED backup cascades and deletes subsequent COMPLETE backups
> --------------------------------------------------------------------------
>
> Key: HBASE-30054
> URL: https://issues.apache.org/jira/browse/HBASE-30054
> Project: HBase
> Issue Type: Bug
> Components: backup&restore
> Reporter: Hernan Romer
> Assignee: mazhengxuan
> Priority: Major
> Labels: pull-request-available
>
> When a backup fails, failBackup restores the backup system table from a
> snapshot taken before the backup started. This rolls back all state changes
> (WAL timestamps, etc.), so the FAILED backup was never part of the backup
> chain. No subsequent backup depends on it.
>
>
> However, BackupAdminImpl.deleteBackup unconditionally runs cascade logic via
> getAffectedBackupSessions, which finds all incremental backups newer than the
> deleted backup (up to the next full). When the deleted backup is FAILED, this
> cascade incorrectly identifies subsequent COMPLETE incrementals as "affected"
> and deletes them via removeTableFromBackupImage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
