You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Kevin Geiszler (Jira)" <ji...@apache.org> on 2025/08/07 02:56:00 UTC
[jira] [Commented] (HBASE-29447) WAL Archives Cause Incremental Backup Failures
[ https://issues.apache.org/jira/browse/HBASE-29447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18012466#comment-18012466 ]
Kevin Geiszler commented on HBASE-29447:
----------------------------------------
I was seeing this error in IntegrationTestBackupRestore. Although, I didn't see it right away because the exception was happening in a separate thread and not the test to fail. I have reported this observation in HBASE-29503.
> WAL Archives Cause Incremental Backup Failures
> ----------------------------------------------
>
> Key: HBASE-29447
> URL: https://issues.apache.org/jira/browse/HBASE-29447
> Project: HBase
> Issue Type: Bug
> Components: backup&restore
> Reporter: Hernan Gelaf-Romer
> Assignee: Hernan Gelaf-Romer
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 2.7.0, 3.0.0-beta-2, 2.6.4
>
>
> If a WAL file is rolled + archived during an incremental backup, we get a FNFE and the backup process will fail. When we try to run the WalPlayer to convert WAL files to HFiles, we run into the following error
>
> {code:java}
> 2025-07-06 11:39:22.573 [pool-115-thread-1] ERROR o.a.h.h.b.impl.TableBackupClient - Unexpected exception in incremental-backup: incremental copy backup_1751801939412File hdfs://venus-hb2-a-prod:8020/hbase/WALs/na1-real-weary-skink.iad02.hubinternal.net,60020,1751589560526/na1-real-weary-skink.iad02.hubinternal.net%2C60020%2C1751589560526.1751800206074 does not exist. java.io.FileNotFoundException: File hdfs://venus-hb2-a-prod:8020/hbase/WALs/na1-real-weary-skink.iad02.hubinternal.net,60020,1751589560526/na1-real-weary-skink.iad02.hubinternal.net%2C60020%2C1751589560526.1751800206074 does not exist.{code}
>
> In order to make this more resilient, we could make sure to check the archive directory for the missing WAL file if we run into this issue. We do something similar when handling bulkloads
--
This message was sent by Atlassian Jira
(v8.20.10#820010)