[
https://issues.apache.org/jira/browse/ZOOKEEPER-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated ZOOKEEPER-688:
------------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this. thanks pat!
> explain session expiration better in the docs & faq
> ---------------------------------------------------
>
> Key: ZOOKEEPER-688
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-688
> Project: Zookeeper
> Issue Type: Bug
> Components: documentation
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Priority: Critical
> Fix For: 3.3.0
>
> Attachments: ZOOKEEPER-688.patch, ZOOKEEPER-688.patch
>
>
> We are not clear enough (and the diagram we do have seems misleading) on
> _when_ session expirations are generated. In particular the fact that you
> only get expirations when the client is connected to the cluster, not when
> disconnected.
> we need to detail:
> 1) when do you get expiration
> 2) what is the sequence of events that the watcher sees, from disco state, to
> getting the expiration (say the expiration happens when the client is disco,
> what do you see in the watcher while you are getting reconnected)
> 3) we need to give some examples of how to test this. We should be explicit
> that "pulling the network cable" on the client will not show expiration since
> the cliient will not be reconnected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
