Github user Randgalt commented on the pull request:
https://github.com/apache/curator/pull/97#issuecomment-133976670
> Assume a timing discrepancy between the curator client and ZK server,
such that the client assumes a session is lost by timeout, but in a (racy) way,
the connection is successfully re-established to the server and the server does
not drop the session. Can we be sure to resolve this race, such that if session
lost events have already fired or started firing, the client forcibly creates a
new session instead of using the old one?
This isn't an issue because when the LOST state is generated the current
client is also closed so the session will expire in any event.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
