Using Curator to implements a distributed mutex. if the client who already acquire the mutex is disconnect with zk server due to a network failure, then Curator will trying to reconnect. let's assume it's finally successful reconnected, but the last session is expired and the ephemeral lock node used for mutex is also disappeared, then this mutex not work again!
So how can I handle mutex fail after reconnect when using Curator? Thanks for ur reply. --Sig
