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-324) TreeCache sending multiple NODE_ADDED events for same node
Date Fri, 20 May 2016 02:32:12 GMT

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

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

Github user dragonsinth commented on the pull request:

    https://github.com/apache/curator/pull/148#issuecomment-220502769
  
    Weird, I don't know what's up with the branch syncing.
    
    Basically, the root node transitions between LIVE <-> DEAD depending on whether
it exists or not.  Child nodes can only transition PENDING -> LIVE -> DEAD; a child
node isn't allowed to go from DEAD -> LIVE; instead it's replaced with a new child node
at the same spot.  That's the source of the double event, I think, although I didn't dig deep
enough to fully understand it.  So this test is saying, if you're going PENDING -> LIVE
then fire an ADD event; if you're the root then DEAD -> LIVE is allowed to fire an ADD
event too.


> TreeCache sending multiple NODE_ADDED events for same node
> ----------------------------------------------------------
>
>                 Key: CURATOR-324
>                 URL: https://issues.apache.org/jira/browse/CURATOR-324
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 3.1.0, 2.10.0
>            Reporter: Jordan Zimmerman
>            Assignee: Scott Blum
>
> details coming in the next 10 min - I will push a test



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message