[
https://issues.apache.org/jira/browse/HBASE-15411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205587#comment-15205587
]
Enis Soztutar commented on HBASE-15411:
---------------------------------------
To those of us following the backup work, this patch comes on top of
HBASE-14030 patch and moves the backup execution to the server side. Phase 2
combined patch (HBASE-14123) comes on top of this. So ordering is HBASE-14030
-> HBASE-15411 -> HBASE-14123.
Phase 1 patch (HBASE-14030) is not committed yet, since I would like to see the
actual fixes to move the logic to server side and make sure that the backup
file layout and PB data structures, file manifests, etc, are as feature-proof
as it can be.
However, there is still some need to put this and HBASE-14123 on review board
so that reviewers can get a sense of what is going on. Let me see what can be
done there.
> Rewrite backup with Procedure V2
> --------------------------------
>
> Key: HBASE-15411
> URL: https://issues.apache.org/jira/browse/HBASE-15411
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 15411-v1.txt, 15411-v11.txt, 15411-v12.txt,
> 15411-v13.txt, 15411-v14.txt, 15411-v15.txt, 15411-v16.txt, 15411-v18.txt,
> 15411-v3.txt, 15411-v5.txt, 15411-v6.txt, 15411-v7.txt, 15411-v9.txt,
> FullTableBackupProcedure.java
>
>
> Currently full / incremental backup is driven by BackupHandler (see call()
> method for flow).
> This issue is to rewrite the flow using Procedure V2.
> States (enum) for full / incremental backup would be introduced in
> Backup.proto which correspond to the steps performed in BackupHandler#call().
> executeFromState() would pace the backup based on the current state.
> serializeStateData() / deserializeStateData() would be used to persist state
> into procedure WAL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
