[
https://issues.apache.org/jira/browse/CURATOR-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Zimmerman closed CURATOR-377.
------------------------------------
Resolution: Won't Fix
This would be better handled directly in ZooKeeper. There's already an issue
for it. ZOOKEEPER-2368
> Curator should have an option to send KeeperState.Expired to watchers when a
> ZK handle is closed
> ------------------------------------------------------------------------------------------------
>
> Key: CURATOR-377
> URL: https://issues.apache.org/jira/browse/CURATOR-377
> Project: Apache Curator
> Issue Type: Improvement
> Reporter: Jordan Zimmerman
> Assignee: Jordan Zimmerman
>
> Curator manages the ZooKeeper handle internally. Under certain circumstances,
> Curator will close the current ZooKeeper handle and create a new one.
> However, any set Watchers in the old ZooKeeper handle will never get
> triggered. If code is expecting a trigger - even for KeeperState.Expired - it
> will never happen. Curator should have an option to, when closing the
> ZooKeeper handle, fake KeeperState.Expired messages to any pending Watchers
> so that they know to exit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
