curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dragonsinth <...@git.apache.org>
Subject [GitHub] curator pull request: [CURATOR-324] Test for event ordering in bot...
Date Fri, 20 May 2016 02:31:16 GMT
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.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message