[
https://issues.apache.org/jira/browse/HBASE-28449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831062#comment-17831062
]
Hudson commented on HBASE-28449:
--------------------------------
Results for branch branch-3
[build #172 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/172/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/172/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/172/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/172/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Fix BackupSystemTable Scans
> ----------------------------
>
> Key: HBASE-28449
> URL: https://issues.apache.org/jira/browse/HBASE-28449
> Project: HBase
> Issue Type: Bug
> Reporter: Briana Augenreich
> Assignee: Briana Augenreich
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.0, 3.0.0-beta-2
>
>
> When calculating which WALs should be included in an incremental backup the
> backup system does a prefix scan for the last roll log timestamp. This uses
> the backup root in the prefix (<prefix><backupRoot>.) If you happen have
> multiple backup roots where one is a root of the other you'll get inaccurate
> results.
>
> Since the rowkey is <prefix><backupRoot><null separator><server> let's modify
> the prefix scan to be <prefix><backupRoot><null separator>.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
