You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Vinayak Hegde (Jira)" <ji...@apache.org> on 2025/06/13 09:38:00 UTC

[jira] [Assigned] (HBASE-29219) Ignore Empty WAL Files While Consuming Backed-Up WAL Files

     [ https://issues.apache.org/jira/browse/HBASE-29219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinayak Hegde reassigned HBASE-29219:
-------------------------------------

    Assignee: Vinayak Hegde  (was: asolomon)

> Ignore Empty WAL Files While Consuming Backed-Up WAL Files
> ----------------------------------------------------------
>
>                 Key: HBASE-29219
>                 URL: https://issues.apache.org/jira/browse/HBASE-29219
>             Project: HBase
>          Issue Type: Task
>          Components: backup&amp;restore
>            Reporter: Vinayak Hegde
>            Assignee: Vinayak Hegde
>            Priority: Major
>
> Currently, {{ContinuousBackupReplicationEndpoint}} creates WAL files in the backup location and continuously writes incoming WAL entries.
> These WAL files are consumed during *Point-In-Time Recovery (PITR)* and {*}incremental backups{*}. However, an edge case may arise:
> If we attempt to access a WAL file that is currently {*}empty{*}—for instance, when the *Continuous Backup Replication Endpoint* closes a file, reopens a new one for writing, but has not yet written any data—an exception occurs. The WAL file reader throws an error indicating that the {*}WAL PB magic is missing{*}.
> To handle this, we need to *skip/ignore empty WAL files* and continue processing the remaining files without interruption.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)