curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-332) Internal watcher tracking for new WatcherRemoveCuratorFramework feature is not correct
Date Thu, 26 May 2016 18:40:12 GMT

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

Scott Blum commented on CURATOR-332:
------------------------------------

Interesting.. wonder if this is why the treecache race was showing up on 3.0 and not master.
 I noticed a big difference was in how watchers were removed on deletion.

> Internal watcher tracking for new WatcherRemoveCuratorFramework feature is not correct
> --------------------------------------------------------------------------------------
>
>                 Key: CURATOR-332
>                 URL: https://issues.apache.org/jira/browse/CURATOR-332
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework, Recipes
>    Affects Versions: 3.1.0
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>             Fix For: 3.2.0
>
>
> The WatcherRemoveCuratorFramework introduced in 3.0.0 doesn't track watchers correctly
and can sometimes lose track of some watchers and, thus, not delete them when requested to.
Examples:
> * Exists watchers stay set even when there is a NoNode exception
> * If a watcher is successfully set and then the same watcher is used during a network
failure, WatcherRemoveCuratorFramework will clear the watcher internally.



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

Mime
View raw message