You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2024/03/25 19:38:00 UTC

[jira] [Resolved] (HBASE-28449) Fix BackupSystemTable Scans

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

Bryan Beaudreault resolved HBASE-28449.
---------------------------------------
    Fix Version/s: 2.6.0
                   3.0.0-beta-2
       Resolution: Fixed

Pushed to branch-2.6+. Thanks [~baugenreich]!

> 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)