Skip to content

HBASE-30037: FullTableBackupClient should not delete bulk load tracking entries before backup completion#7994

Open
nazuhifu wants to merge 1 commit intoapache:masterfrom
nazuhifu:HBASE-30037
Open

HBASE-30037: FullTableBackupClient should not delete bulk load tracking entries before backup completion#7994
nazuhifu wants to merge 1 commit intoapache:masterfrom
nazuhifu:HBASE-30037

Conversation

@nazuhifu
Copy link
Copy Markdown

JIRA: HBASE-30037

Move deleteBulkLoadedRows() to execute only after completeBackup() so bulk load tracking rows are removed only when the full backup has completed successfully

Add regression test to ensure bulk load tracking rows are not removed if full backup fails

backupManager
.deleteBulkLoadedRows(bulkLoadsToDelete.stream().map(BulkLoad::getRowKey).toList());
} catch (Exception e) {
failBackup(conn, backupInfo, backupManager, e, "Unexpected BackupException : ",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @nazuhifu

What happens if the backup completes successfully but a failure occurs during the deleteBulkLoadedRows call? In that case, it appears the operation is reported as a BackupFailure, even though the backup itself succeeded and only the post-cleanup step failed.

Can we improve this behavior to distinguish between backup success and cleanup failure?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants