Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Fri, 17 Jul 2015 22:28:04 +0000 (UTC)
From: "Vladimir Rodionov (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12843268.1436294470000.222989.1437172084675@Atlassian.JIRA>
In-Reply-To: <JIRA.12843268.1436294470000@Atlassian.JIRA>
References: <JIRA.12843268.1436294470000@Atlassian.JIRA>
 <JIRA.12843268.1436294470586@arcas>
Subject: [jira] [Resolved] (HBASE-14036) HBase Backup/Restore Phase 1:
 Custom WAL archive cleaner
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vladimir Rodionov resolved HBASE-14036.
---------------------------------------
    Resolution: Implemented

This feature is part of patch v4. See parent JIRA.

> HBase Backup/Restore Phase 1: Custom WAL archive cleaner
> --------------------------------------------------------
>
>                 Key: HBASE-14036
>                 URL: https://issues.apache.org/jira/browse/HBASE-14036
>             Project: HBase
>          Issue Type: Task
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>             Fix For: 2.0.0
>
>
> Custom WAL archive cleaner (BackupLogCleaner).  We need to keep WAL files in archive until they either get copied over to backup destination during an incremental backup or full backup (for ALL tables) happens. This is tricky, but is doable. Backup-aware WAL archiver cleaner should consult hbase:backup to determine if WAL file is safe to purge.


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