Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 14 May 2014 20:25:16 +0000 (UTC)
From: "Demai Ni (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12714278.1400099065047.348382.1400099116183@arcas>
In-Reply-To: <JIRA.12714278.1400099065047@arcas>
References: <JIRA.12714278.1400099065047@arcas>
Subject: [jira] [Created] (HBASE-11172) Cancal a backup process
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Demai Ni created HBASE-11172:
--------------------------------

             Summary: Cancal a backup process 
                 Key: HBASE-11172
                 URL: https://issues.apache.org/jira/browse/HBASE-11172
             Project: HBase
          Issue Type: New Feature
    Affects Versions: 0.99.0
            Reporter: Demai Ni
             Fix For: 0.99.0


h2. Feature Description
the jira is part of  [HBASE-7912|https://issues.apache.org/jira/browse/HBASE-7912], and depend on full backup [HBASE-10900| https://issues.apache.org/jira/browse/HBASE-10900] and incremental backup [HBASE-11085| https://issues.apache.org/jira/browse/HBASE-11085]. for the detail layout and frame work, please reference to  [HBASE-10900|  https://issues.apache.org/jira/browse/HBASE-10900].

A backup operation may need to move handreds/thousands GB of data, and takes hours. Sometimes, the operation may take longer than the original maintenance time window planned by the administration. So it is necessary to have the functionality to cancel the operation and reset all the history/manifest info whenever necessary. so that we can have a clean backup in the next time window 


--
This message was sent by Atlassian JIRA
(v6.2#6252)