curator-dev mailing list archives

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

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

ASF GitHub Bot commented on CURATOR-33:
---------------------------------------

Github user Randgalt commented on the pull request:

    https://github.com/apache/curator/pull/17#issuecomment-50918629
  
    Imagine a scenario where there is a temporary connection problem. Curator will send SUSPENDED.
If the connect gets repaired and the session survives, Curator will send RECONNECTED. At nearly
the same time, some of the watchers might get called due to watched changes. Thus, a method
like refreshData() might get called simultaneously by two threads.


> Recursive Node Cache
> --------------------
>
>                 Key: CURATOR-33
>                 URL: https://issues.apache.org/jira/browse/CURATOR-33
>             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
(v6.2#6252)

Mime
View raw message