Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 9 Aug 2017 19:38:00 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.13093582.1502307436000.131847.1502307480357@Atlassian.JIRA>
In-Reply-To: <JIRA.13093582.1502307436000@Atlassian.JIRA>
References: <JIRA.13093582.1502307436000@Atlassian.JIRA> <JIRA.13093582.1502307436445@jira-lw-us.apache.org>
Subject: [jira] [Created] (HBASE-18547) Provide better cleanup of WAL
 related entries in backup table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 09 Aug 2017 19:38:06 -0000

Ted Yu created HBASE-18547:
------------------------------

             Summary: 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 files 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)