[ 
https://issues.apache.org/jira/browse/HBASE-29776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18128092#comment-18128092
 ] 

Hudson commented on HBASE-29776:
--------------------------------

Results for branch branch-2
        [build #174 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase-Integration-Test/job/branch-2/174/]:
 (/) *{color:green}+1 overall{color}*
----
details (if available):



(/) {color:green}+1 client integration test for 2.10.2 {color}


(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.5 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.3.6 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.0 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.1 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.2 {color}
(/) {color:green}+1 client integration test for 3.4.2 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.3 {color}
(/) {color:green}+1 client integration test for 3.4.3 with shaded hadoop 
client{color}


> Log filtering in IncrementalBackupManager can lead to data loss
> ---------------------------------------------------------------
>
>                 Key: HBASE-29776
>                 URL: https://issues.apache.org/jira/browse/HBASE-29776
>             Project: HBase
>          Issue Type: Improvement
>          Components: backup&restore
>            Reporter: Hernan Romer
>            Priority: Major
>              Labels: pull-request-available
>
> At the moment, incremental backups will filter out old wals that belong to RS 
> which do not have any active WAL files. 
>  
> The code 
>  
> {code:java}
> // It is possible that a host in .oldlogs is an obsolete region server
> // so newestTimestamps.get(host) here can be null.
> // Even if these logs belong to a obsolete region server, we still need
> // to include they to avoid loss of edits for backup.
> Long newTimestamp = newestTimestamps.get(host);
> if (newTimestamp == null || currentLogTS > newTimestamp) {
>   newestLogs.add(currentLogFile);
> }{code}
> Is doing the opposite of what the comment (correctly) says. 



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

Reply via email to