curator-dev mailing list archives

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


Scott Blum commented on CURATOR-319:

I actually have to agree with Tommy in principle.  It makes sense for most of the recipes
to create parent paths when needed, but I really can't think of a good reason for anything
in the recipes.cache package to modify ZK at all.  I don't know why we added a createParents
option to TreeCache.

> NodeCache recreates deleted parents of the node being cached
> ------------------------------------------------------------
>                 Key: CURATOR-319
>                 URL:
>             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:
> This was not the behavior prior to 2.10.0, and seems pretty unexpected.

This message was sent by Atlassian JIRA

View raw message