You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2024/03/25 18:47:00 UTC
[jira] [Assigned] (HBASE-28456) HBase Restore restores old data if data for the same timestamp is in different hfiles
[ https://issues.apache.org/jira/browse/HBASE-28456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Beaudreault reassigned HBASE-28456:
-----------------------------------------
Assignee: Bryan Beaudreault
> HBase Restore restores old data if data for the same timestamp is in different hfiles
> -------------------------------------------------------------------------------------
>
> Key: HBASE-28456
> URL: https://issues.apache.org/jira/browse/HBASE-28456
> Project: HBase
> Issue Type: Bug
> Components: backup&restore
> Affects Versions: 2.6.0, 3.0.0
> Reporter: Ruben Van Wanzeele
> Assignee: Bryan Beaudreault
> Priority: Blocker
> Attachments: ChangesOnHFilesOnSameTimestampAreNotCorrectlyRestored.java
>
>
> The restore brings back 'old' data when executing restore.
> It feels like the hfile sequence id is not respected during the restore.
> See testing code attached. The workaround solution is to trigger major compaction before doing the backup (not really feasible for daily backups)
> We didn't investigate this yet, but this might also impact the merge of multiple incremental backups (since that follows a similar code path merging hfiles).
> This currently blocks our support for HBase backup and restore.
> Willing to participate in a solution if necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)