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

Himanshu Vashishtha commented on HBASE-9141:
--------------------------------------------

The attached patch has the following changes:

1) Include a test cases where it create-->serializes-->delete existing--> 
restores znodes. It checks whether the data is restored or not, etc.

2) The znodes are saved with relative path, starting from replication base 
znode (by default, from replication/). This is useful in case a user wants to 
restore under a different hbase root znode.

3) Options to delete existing znode (after taking the backup, or before 
restoring the znodes); option to delete the backup file after successful 
restoration.

4) Other nits suggested by Ted. More help documentation on "moving" znodes.


                
> Replication Znodes Backup Tool
> ------------------------------
>
>                 Key: HBASE-9141
>                 URL: https://issues.apache.org/jira/browse/HBASE-9141
>             Project: HBase
>          Issue Type: Improvement
>          Components: migration, Replication
>    Affects Versions: 0.94.10
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>             Fix For: 0.95.2
>
>         Attachments: HBase-9141.patch
>
>
> While migrating to 0.96, we recommend deleting old znodes so users not face 
> issues like HBASE-7766, and let HBase create them out of box.
> Though HBase tends to store only ephemeral data in zookeeper, replication has 
> a different approach. Almost all of its data (state, peer info, logs, etc) is 
> present in zookeeper. We would like to preserve them in order to not do 
> re-adding of peers, and ensuring complete replication after we have migrated 
> to 0.96. 
> This jira adds a tool to serialize/de-serialize replication znodes to the 
> underlying filesystem. This could be used while migrating to 0.96.0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to