hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15094) Selection of WAL files eligible for incremental backup is broken
Date Wed, 13 Jan 2016 19:38:39 GMT

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

Jerry He commented on HBASE-15094:
----------------------------------

I thought that incremental backup was not for individual table separately.
In this case, when you carry out the first incremental backup, it is an incremental backup
for both T1 and T2.
Most likely or not, the WALs are shared and overlapping.


> Selection of WAL files eligible for incremental backup is broken
> ----------------------------------------------------------------
>
>                 Key: HBASE-15094
>                 URL: https://issues.apache.org/jira/browse/HBASE-15094
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>             Fix For: 2.0.0
>
>
> We should add to a selection WAL files which have been copied over by different backup
sessions and which are newer than the most recent files processed for a given table. Currently,
we look for WAL files only in a files system (WALs and OldWALs directories)
> Scenario
> Full Backup T1
> Full Backup T2
>  Created WAL1
> Incremental Backup T1 (WAL1 becomes eligible for deletion)
> some time later
> Incremental Backup T2 (WAL1 can be deleted by this time and won't get it into WAL file
list for T2)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message