curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Njal Karevoll (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-258) PersistentEphemeralNode stops watching after first WatchedEvent
Date Fri, 18 Sep 2015 11:37:04 GMT

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

Njal Karevoll commented on CURATOR-258:
---------------------------------------

Anyone able to have a look at this? The error seems it was introduced by the change here:
https://github.com/apache/curator/pull/50/files

> PersistentEphemeralNode stops watching after first WatchedEvent
> ---------------------------------------------------------------
>
>                 Key: CURATOR-258
>                 URL: https://issues.apache.org/jira/browse/CURATOR-258
>             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
>
> 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
(v6.3.4#6332)

Mime
View raw message