curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CURATOR-33) Recursive Node Cache
Date Fri, 01 Aug 2014 18:25:38 GMT


ASF GitHub Bot commented on CURATOR-33:

Github user dragonsinth commented on the pull request:
    So I looked through the issue you described with respect to wasReconnected() being called
concurrently with refreshData / refreshChildren.  I can't actually see any potential problems
with this.  None of the code paths from wasReconnected()/wasCreated()/wasDeleted() perform
any mutations, all they ultimately do is queue up ZK operations which fire on the serialized
background response thread.  The background response thread is the only thread that mutates
the tree.
    Do you see something I'm missing?

> Recursive Node Cache
> --------------------
>                 Key: CURATOR-33
>                 URL:
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>            Reporter: John Vines
>            Assignee: Jordan Zimmerman
>             Fix For: TBD
>         Attachments: CURATOR-33.2.patch, CURATOR-33.patch
> Currently the PathChildrenCache will trigger listen events for all children at the given
node. However, it would be useful to have a cache that would trigger listen events for the
entire hierarchy below the given node.

This message was sent by Atlassian JIRA

View raw message