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 Wed, 25 Sep 2013 16:46:02 GMT

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

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

The problem there is that you have to make a call on each individual node to get the Stat
object. So, there's no way to do this "inline". All the details have to be fetched and then
you can construct the ordering. This suggests a higher-level recipe that uses PathChildrenCache
internally. It could wait until node changes settle or a pre-defined timing threshold and
then construct a new message with the ordering that you need.
                
> 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