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/31 07:09:45 UTC
[jira] [Resolved] (CURATOR-185) Create a LOST_SESSION connection
state
[ https://issues.apache.org/jira/browse/CURATOR-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jordan Zimmerman resolved CURATOR-185.
--------------------------------------
Resolution: Won't Fix
CURATOR-246 will handle this
> Create a LOST_SESSION connection state
> --------------------------------------
>
> Key: CURATOR-185
> URL: https://issues.apache.org/jira/browse/CURATOR-185
> Project: Apache Curator
> Issue Type: New Feature
> Components: Client
> Affects Versions: 2.7.1
> Reporter: Benjamin Jaton
>
> Since the LOST connection state doesn't have anything to do with the loss of the ZK session, it would be very useful to have an event for it.
> Suggested implementation to detect the loss of session:
> - Upon reception of the SUSPENDED state, start a timer
> - if we receive a RECONNECTED event, check the session ID. If we have a different session ID, then our session has been lost
> - if we didn't receive a RECONNECTED event and the time reaches <sessionTimeoutMs>, our session is lost
> That should inform the user of the loss of a session in a timely fashion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)