curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <>
Subject [jira] [Resolved] (CURATOR-258) PersistentEphemeralNode stops watching after first WatchedEvent
Date Sun, 11 Oct 2015 20:52:05 GMT


Jordan Zimmerman resolved CURATOR-258.
       Resolution: Fixed
         Assignee: Jordan Zimmerman
    Fix Version/s: 2.9.1

> PersistentEphemeralNode stops watching after first WatchedEvent
> ---------------------------------------------------------------
>                 Key: CURATOR-258
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 3.0.0, 2.8.0, 2.9.0, 2.9.1
>            Reporter: Njal Karevoll
>            Assignee: Jordan Zimmerman
>             Fix For: 3.0.0, 2.9.1
> The `Watcher` in the `PersistentEphemeralNode` recipe only reacts to the `NodeDeleted`
event. But it's possible to receive a `NodeDataChanged` event as well due to
>  1. The node has been created before the recipe has been started, so the first event
it receives is it's own update.
>  2. The node has been created by another session, and the recipe accepts updating nodes
belonging to a different session. In this case, it also receives it's own update in the `Watcher`,
and no longer watches the node when the `NodeDeleted` event comes through (after the session
of the other client expires). This is easily reproducible by restarting a service using a
the recipe when the session timeout is higher than the service restart time. 

This message was sent by Atlassian JIRA

View raw message