[
https://issues.apache.org/jira/browse/HBASE-29984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104578#comment-18104578
]
Hudson commented on HBASE-29984:
--------------------------------
Results for branch master
[build #1486 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1486/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1486/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1486/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> Backup log collection can fail
> ------------------------------
>
> Key: HBASE-29984
> URL: https://issues.apache.org/jira/browse/HBASE-29984
> Project: HBase
> Issue Type: Bug
> Components: backup&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
> Fix For: 4.0.0-alpha-1
>
>
> 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)
