Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 6 Jul 2017 03:22:03 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12846684.1437512831000.180271.1499311323568@Atlassian.JIRA>
In-Reply-To: <JIRA.12846684.1437512831000@Atlassian.JIRA>
References: <JIRA.12846684.1437512831000@Atlassian.JIRA> <JIRA.12846684.1437512831488@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-14135) HBase Backup/Restore Phase 3:
 Merge backup images
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 06 Jul 2017 03:22:09 -0000


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

stack commented on HBASE-14135:
-------------------------------

bq. Long running tests are well-known issue for us.

And? What is the intent? To change them? Thanks.

bq. No it is just a generic Job which can be configured and executed

You understand how someone might think 'MR' when they see 'Job'. Do you want to prevent any confusion?

bq. Yes, it is synchronous. All operations are client-driven.

And if the client goes away? They query to find running jobs?


> HBase Backup/Restore Phase 3: Merge backup images
> -------------------------------------------------
>
>                 Key: HBASE-14135
>                 URL: https://issues.apache.org/jira/browse/HBASE-14135
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>            Priority: Blocker
>              Labels: backup
>             Fix For: HBASE-7912
>
>         Attachments: HBASE-14135-v1.patch, HBASE-14135-v3.patch
>
>
> User can merge incremental backup images into single incremental backup image.
> # Merge supports only incremental images
> # Merge supports only images for the same backup destinations
> Command:
> {code}
> hbase backup merge image1,image2,..imageK
> {code}
> Example:
> {code}
> hbase backup merge backup_143126764557,backup_143126764456 
> {code}
> When operation is complete, only the most recent backup image will be kept (in above example -  backup_143126764557) as a merged backup image, all other images will be deleted from both: file system and backup system tables, corresponding backup manifest for the merged backup image will be updated to remove dependencies from deleted images. Merged backup image will contains all the data from original image and from deleted images.


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