curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-57) Event order lost with PathChildrenCache
Date Thu, 26 Sep 2013 15:06:06 GMT

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

Jordan Zimmerman commented on CURATOR-57:
-----------------------------------------

PathChildrenCache works this way already. The issue is how you determine when to send messages?
In a dynamic ZK ensemble nodes are being changed all the time. You could send messages after
each getChildren() batch is processed but this is arbitrary. Also, in order to truly ensure
ordering you'd likely need to re-query ZooKeeper inside of the Watchers which is an anti-pattern
(see https://cwiki.apache.org/confluence/display/CURATOR/TN1).
                
> Event order lost with PathChildrenCache
> ---------------------------------------
>
>                 Key: CURATOR-57
>                 URL: https://issues.apache.org/jira/browse/CURATOR-57
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.0.1-incubating
>         Environment: Ubuntu 10.10
>            Reporter: Benjamin Jaton
>             Fix For: awaiting-response
>
>         Attachments: Test.java
>
>
> I am attaching a simple test to demonstrate the problem:
> Single threaded 'for' loop that creates children 0 to N, the events are not received
in order.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message