You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/07/29 06:45:00 UTC

[jira] [Updated] (HBASE-29984) Backup log collection can fail

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

ASF GitHub Bot updated HBASE-29984:
-----------------------------------
    Labels: pull-request-available  (was: )

> Backup log collection can fail
> ------------------------------
>
>                 Key: HBASE-29984
>                 URL: https://issues.apache.org/jira/browse/HBASE-29984
>             Project: HBase
>          Issue Type: Bug
>          Components: backup&amp;restore
>    Affects Versions: 4.0.0-alpha-1, 3.0.0-beta-2, 2.6.4
>            Reporter: Dieter De Paepe
>            Assignee: mazhengxuan
>            Priority: Major
>              Labels: pull-request-available
>
> Found during [review|https://github.com/apache/hbase/pull/7582/changes/e1c25329acf26792bbf4faed98a44fab647e39d2#r2676601419] of HBASE-29776.
> The backup logic scans the logs and oldlogs:
>  * IncrementalBackupManager#getLogFilesForNewBackup
>  * (Introduced in HBASE-29776) FullTableBackupClient#execute
> It assumes old logs are files under the "oldWals" folder.
> However, there's a configuration key hbase.separate.oldlogdir.by.regionserver that can change this behavior. When set to true, the old logs are stored in directories under "oldWals". The backup code will error on this.



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