[
https://issues.apache.org/jira/browse/HBASE-9141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735719#comment-13735719
]
rajeshbabu commented on HBASE-9141:
-----------------------------------
[~v.himanshu]
Its really good tool.
I have some doubts here, may be silly.
->while restoring don't we need to convert to PB after migrating to 0.96.0 ?
{code}
System.out.println("Restoring znode: " + z);
ZKUtil.createWithParents(zkw, ZKUtil.joinZNode(baseZnode, z.getPath()),
z.getData());
{code}
-> After migration, lets suppose hlogs are splitted and recovered properly,
then still they will be archived to continue replication even if we dont have
replication znodes(peers,queues)? Is this scenario can happen with little delay
in restoring replication znodes? I am new to replication.
> 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, HBase-9141-v1.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
