[CURATOR-332] Internal watcher tracking for new WatcherRemoveCuratorFramework feature is not correct

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.0
• Fix Version/s: 3.2.0
• Component/s: Framework, Recipes
• Assignee: Jordan Zimmerman
• Reporter: Jordan Zimmerman
• Created: 26/May/16 18:04
• Updated: 01/Jun/16 00:09
• Resolved: 01/Jun/16 00:09

Description

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.

Issue Links

• links to: GitHub Pull Request #154