Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Date: Sun, 13 Sep 2015 17:38:13 -0500
From: Jordan Zimmerman <jordan@jordanzimmerman.com>
To: "=?utf-8?Q?dev=40curator.apache.org?=" <dev@curator.apache.org>
Message-ID: <etPan.55f5fad5.4de96b5f.42a@Jordans-MacBook-Pro.local>
Subject: DEVS PLEASE READ: What is the correct timeout for a session
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="55f5fad5_60a8f34e_42a"

--55f5fad5_60a8f34e_42a
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Devs,

Given that Curator 3.0 will try to accurately track the session, I realiz=
e I=E2=80=99m a bit confused about when a session actually expires. In th=
e implementation I pushed, a timer starts when=C2=A0Watcher.Event.KeeperS=
tate.Disconnected is seen. Then, if the negotiated session timeout elapse=
s, Curator simulates a session expiration. However, the timeout is based =
on the saved time when Disconnected is seen. I=E2=80=99ve been searching =
in the ZK code and it=E2=80=99s hard to tell if that=E2=80=99s correct. I=
=E2=80=99d appreciate a few other eyes on this. The significant class in =
ZK is SessionTrackerImpl.java. touchSession() is called periodically and =
a kind of priority queue is used to pull out expiring sessions.

Thanks=21

-Jordan


--55f5fad5_60a8f34e_42a--