hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Rodionov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14135) HBase Backup/Restore Phase 3: Merge backup images
Date Fri, 07 Jul 2017 00:35:00 GMT

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

Vladimir Rodionov commented on HBASE-14135:

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

Yes. There is a JIRA HBASE-16458.
You understand how someone might think 'MR' when they see 'Job'. Do you want to prevent any

We have had already long discussion about this topic in the past. Should we start it again?

Originally it was Service, then - Task, now is Job. What do you suggest, stack?

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

Job will fail, but next time (run), repair will be started automatically (mostly cleanup stuff).
We have repair tool, just in case if "client goes away" or some other disaster happens.  

> 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

View raw message