You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/01 00:07:12 UTC
[jira] [Commented] (CURATOR-332) Internal watcher tracking for new
WatcherRemoveCuratorFramework feature is not correct
[ https://issues.apache.org/jira/browse/CURATOR-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308925#comment-15308925 ]
ASF GitHub Bot commented on CURATOR-332:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/curator/pull/154
> 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)