[
https://issues.apache.org/jira/browse/HBASE-28456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830714#comment-17830714
]
Bryan Beaudreault commented on HBASE-28456:
-------------------------------------------
Yea I’m working on the 2.6.0 now, so reporting this bug was good timing. 2.6.0
is the first main release with this feature and I think this bug is critical
enough to block. So my hope is resolve this and cherry to pick to 2.6 asap so I
can continue the release.
The incremental test would be great, thanks!
> 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
> Labels: pull-request-available
> 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)
