[
https://issues.apache.org/jira/browse/HBASE-28706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862490#comment-17862490
]
Dieter De Paepe commented on HBASE-28706:
-----------------------------------------
same portion of code
> Tracking of bulk-loads for backup does not work for multi-root backups
> ----------------------------------------------------------------------
>
> Key: HBASE-28706
> URL: https://issues.apache.org/jira/browse/HBASE-28706
> Project: HBase
> Issue Type: Bug
> Components: backup&restore
> Affects Versions: 2.6.0, 3.0.0, 4.0.0-alpha-1
> Reporter: Dieter De Paepe
> Priority: Blocker
>
> Haven't been able to test this yet, but I highly suspect that
> IncrementalTableBackupClient#handleBulkLoad will delete records of the files
> that were bulk loaded, even if those records are still needed for backups in
> other backuproots.
> I base this on the observation that the code for tracking which WALs should
> be kept around, and backup metadata in general, are all tracked per
> individual backuproot. But for the tracking of bulk uploads, this is not the
> case.
> The result would be data loss (i.e. the bulk loaded data) when taking backups
> across different backuproots.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
