Ouch, is this the current ZK behavior? This is unexpected, if the client get partitioned from ZK cluster, he should get notified and take some action(e.g. commit suicide) otherwise how to tell a ephemeral node is really up or down? Zombie can create synchronization nightmares..
On Mon, Aug 16, 2010 at 7:22 PM, Dave Wright <wrig...@gmail.com> wrote: > Another possible cause for this that I ran into recently with the c client - > you don't get the session expired notification until you are reconnected to > the quorum and it informs you the session is lost. If you get disconnected > and can't reconnect you won't get the notification. Personally I think the > client api should track the session expiration time locally and information > you once it's expired. > > On Aug 16, 2010 2:09 AM, "Qing Yan" <qing...@gmail.com> wrote: > > Hi Ted, > > Do you mean GC problem can prevent delivery of SESSION EXPIRE event? > Hum...so you have met this problem before? > I didn't see any OOM though, will look into it more. > > > On Mon, Aug 16, 2010 at 12:46 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: >> I am assuming that y... >
