[
https://issues.apache.org/jira/browse/HBASE-9141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740055#comment-13740055
]
Himanshu Vashishtha commented on HBASE-9141:
--------------------------------------------
Yes, for this I avoided using multi here. And, using -deleteOldZnode option, we
would not need it as it will remove any leftover znodes from the previous run.
The upgrade is not considered complete if there is some error while doing it.
And in case of any exception while doing it, it throws the error. So, a user
would run it again unless it is successful.
For the overlap, if we go the route of upgrading znodes to pb, we don't need
this. If we go the route of clearing zk data and letting hbase re-create it, we
do need this.
I know the above statement is open as to how we want to handle old znodes
(transform or re-create). I would like to let hbase re-create them (just start
afresh), but let me take a closer look at the protobuffing route.
> 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
