You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Tommy Becker (JIRA)" <ji...@apache.org> on 2016/04/28 20:43:12 UTC

[jira] [Updated] (CURATOR-319) NodeCache recreates deleted parents of the node being cached

     [ https://issues.apache.org/jira/browse/CURATOR-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tommy Becker updated CURATOR-319:
---------------------------------
    Summary: NodeCache recreates deleted parents of the node being cached  (was: NodeCache recreates parents of the node being cached)

> 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)