[
https://issues.apache.org/jira/browse/ZOOKEEPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615808#action_12615808
]
Mahadev konar commented on ZOOKEEPER-84:
----------------------------------------
james,
here is what the current sematics is ---
- there is one on one mapping between a client and a session
- if a session expires the client becomes invalid
- the client can reconnect to the servers if they die only to renew the
session. If the session is invalid this client in invalid.
originally we allowed a client to reconnect and create a new session and foudn
that our users were getting more and more confused with such kind of sematincs
and found that the above sematics made things easier for them. So I think we
should not reconnect and try creating a new session with the same client. does
that make sense?
> provide a mechanism to reconnect a ZooKeeper if a client receives a
> SessionExpiredException
> -------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-84
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-84
> Project: Zookeeper
> Issue Type: Improvement
> Components: java client
> Reporter: james strachan
> Assignee: james strachan
> Attachments: reconnect_patch.patch
>
>
> am about to attach a patch which adds a reconnect() method to easily
> re-establish a connection if a session expires - along with a toString()
> implementation for easier debugging
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
