curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-319) NodeCache recreates deleted parents of the node being cached
Date Mon, 02 May 2016 18:27:13 GMT

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

Scott Blum commented on CURATOR-319:
------------------------------------

I understand in the past there may have been an issue with leaking 'exist' watches set for
nodes that don't exist on the server?  I *think* that all the work that's gone into restructuring
client-side watches in Curator, combined with the addition of the ZK removeWatches should
allow handling that issue?

> NodeCache recreates deleted parents of the node being cached
> ------------------------------------------------------------
>
>                 Key: CURATOR-319
>                 URL: https://issues.apache.org/jira/browse/CURATOR-319
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.10.0
>            Reporter: Tommy Becker
>
> Starting with Curator 2.10.0, the NodeCache will spontaneously re-create parents of the
node being cached if one of them is deleted.  As an example, if there is a NodeCache watching
node /a/b/c and node b is deleted, the cache will immediately recreate node b (but not c)
when the change is processed. This seems to stem from this commit: https://github.com/apache/curator/commit/f02fb225d531506444b54cdf5effb0529a35cdb0
> This was not the behavior prior to 2.10.0, and seems pretty unexpected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message