[
https://issues.apache.org/jira/browse/ZOOKEEPER-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789660#comment-13789660
]
Alexander Shraer commented on ZOOKEEPER-1639:
---------------------------------------------
The context is that I was trying to add a new system znode (for holding the
configuration) and couldn't understand why the new node is initially there but
suddenly disappears! The reason turned out to be that the node I attached it
too is not the one being used after the call to deserializeSnapshot.
I don't think it affects the users - just an internal cleaning up issue.
> zk.getZKDatabase().deserializeSnapshot adds new system znodes instead of
> replacing existing ones
> ------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1639
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1639
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.4.5
> Reporter: Alexander Shraer
>
> Before the call to zk.getZKDatabase().deserializeSnapshot in Learner.java,
> zk.getZKDatabase().getDataTree().getNode("/zookeeper") ==
> zk.getZKDatabase().getDataTree().procDataNode, which means that this is the
> same znode, as it should be.
> However, after this call, they are not equal. The node actually being used in
> client operations is zk.getZKDatabase().getDataTree().getNode("/zookeeper"),
> but the other old node procDataNode is still there and not replaced (in fact
> it is a final field).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
