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

Vladimir Rodionov edited comment on HBASE-14135 at 9/21/16 6:47 PM:
--------------------------------------------------------------------

Two issues with incremental backup implementation:

# Storage usage. WAL files are significantly larger than hfiles, especially 
when compression is enabled in hfiles
# Restore operation time. 

The most significant is the first one. We can that storage reduction factor 
will be something between 3-5 once convert (merge) is implemented.

Running conversion (merge) on a remote destination (cluster) is not feasible in 
many cases, so merge will require reading/writing data back and forth between 
source and destination.

I will postpone this feature until filtering at the source during incremental 
backup is done (HBASE-14141).
 


was (Author: vrodionov):
Two issues with incremental backup implementation:

# Storage usage. WAL files are significantly larger than hfiles, especially 
when compression is enabled in hfiles
# Restore operation time. 

The most significant is the first one. We can that storage reduction factor 
will be something between 3-5 once convert (merge) is implemented.

Running conversion (merge) on a remote destination (cluster) is not feasible in 
many cases, so merge will require reading/writing data back and forth between 
source and destination.

I will postpone this feature until filtering at the source during incremental 
backup is done.
 

> 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
>    Affects Versions: 2.0.0
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>              Labels: backup
>             Fix For: 2.0.0
>
>




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

Reply via email to