You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2015/08/21 04:29:46 UTC
[jira] [Created] (CURATOR-247) Extend Curator's connection state to
support SESSION_LOST
Jordan Zimmerman created CURATOR-247:
----------------------------------------
Summary: Extend Curator's connection state to support SESSION_LOST
Key: CURATOR-247
URL: https://issues.apache.org/jira/browse/CURATOR-247
Project: Apache Curator
Issue Type: Sub-task
Components: Client, Framework
Affects Versions: 2.8.0
Reporter: Jordan Zimmerman
Assignee: Jordan Zimmerman
Fix For: 3.0.0
Currently, Curator has a connection state for LOST that confuses users. It does _not_ mean that the session is lost. Instead it means that the retry policy has given up retrying. Introduce a new connection state that roughly corresponds to the ZooKeeper session expiring. Possibly require that clients request this support via a new new builder method in CuratorFrameworkFactory
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)