I’m not sure what you mean in your OP about committing suicide. But, in the Curator docs, we’ve always recommended assuming you no longer own the lock as soon as SysDisconnected is received.
-Jordan On July 15, 2015 at 2:08:42 PM, Vikas Mehta ([email protected]) wrote: Jordan, We are using it like you describe and don't have a multi-writer problem. Issue is: * Zookeeper ensemble goes into leader election * All clients see session transition to 'CONNECTING' state (SysDisconnected in your sequence) * All clients give up all the locks they owned on the resources they were working with for a GLOBAL outage of the application. -- View this message in context: http://zookeeper-user.578899.n2.nabble.com/locking-leader-election-and-dealing-with-session-loss-tp7581277p7581287.html Sent from the zookeeper-user mailing list archive at Nabble.com.
