Netflix/curator — Issue #10: Connection States
Author: jlaban
Created: 2011-12-07 09:59:31+00:00
State: open

So I could probably start digging through code, but I figured I'd ask:

If my ConnectionStateListener gets sent a LOST state change, is that the equivalent of Zookeeper's SESSION_EXPIRED?

In other words, will I not get a LOST until I actually reconnect to the cluster (which is how SESSION_EXPIRED works) or will I get a LOST right away after the retry policy is exhausted (but perhaps before I reconnect to the cluster)?

I'm hoping it's the latter. I ask because I'm trying to figure out at which point my locks have become garbage: at SUSPENDED or at LOST.

(Ignoring ZK session timeouts vs retry policy lengths for the moment.)

Thanks, and apologies if this is documented somewhere,
John