[jira] [Updated] (HBASE-29350) Ensure Cleanup of Continuous Backup WALs After Last Backup is Force Deleted

["Vinayak Hegde (Jira)" <ji...@apache.org>]

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

Vinayak Hegde updated HBASE-29350:
----------------------------------
    Issue Type: Task  (was: Test)

> Ensure Cleanup of Continuous Backup WALs After Last Backup is Force Deleted
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-29350
>                 URL: https://issues.apache.org/jira/browse/HBASE-29350
>             Project: HBase
>          Issue Type: Task
>          Components: backup&restore
>            Reporter: Vinayak Hegde
>            Assignee: Vinayak Hegde
>            Priority: Major
>
> When the last backup is deleted using the {{-fd}} (force delete) option, there are no remaining backups to recover from. In this state:
>  * Continuous backup metadata in the system table becomes obsolete.
>  * WAL files under the backup WAL directory are no longer needed.
>  * The replication peer used for continuous WAL tracking serves no purpose.
> Since the entire backup chain is gone, we can safely clean up all related metadata and WAL artifacts to free up storage and avoid stale state in the system.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)