You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hernan Romer (Jira)" <ji...@apache.org> on 2026/04/02 16:36:00 UTC

[jira] [Created] (HBASE-30054) Deleting a FAILED backup cascades and deletes subsequent COMPLETE backups

Hernan Romer created HBASE-30054:
------------------------------------

             Summary: 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&amp;restore
            Reporter: Hernan Romer


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)