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

Ted Yu updated HBASE-18547:
---------------------------
    Description: 
I was discussing the design around incremental backup with Vladimir.

Currently if WAL file is recorded in backup table, BackupLogCleaner would 
signal that the file can be cleaned up.
However, cleaner chore doesn't notify BackupLogCleaner whether the file is 
actually deleted.
This means that potentially large number of WAL file entries would stay in 
backup table.

This issue is to investigate better cleanup strategy for the WAL entries.

  was:
I was discussing the design around incremental backup with Vladimir.

Currently if WAL file is recorded in backup table, BackupLogCleaner would 
signal that the file can be cleaned up.
However, cleaner chore doesn't notify BackupLogCleaner whether the file is 
actually deleted.
This means that potentially large number of WAL files would stay in backup 
table.

This issue is to investigate better cleanup strategy for the WAL entries.


> Provide better cleanup of WAL related entries in backup table
> -------------------------------------------------------------
>
>                 Key: HBASE-18547
>                 URL: https://issues.apache.org/jira/browse/HBASE-18547
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>
> I was discussing the design around incremental backup with Vladimir.
> Currently if WAL file is recorded in backup table, BackupLogCleaner would 
> signal that the file can be cleaned up.
> However, cleaner chore doesn't notify BackupLogCleaner whether the file is 
> actually deleted.
> This means that potentially large number of WAL file entries would stay in 
> backup table.
> This issue is to investigate better cleanup strategy for the WAL entries.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to