InterProcessMutex, LeaderLatch, etc use an ephemeral node. If ZooKeeper gives a Disconnected event, the native client reconnects with the same session id, and the ephemeral node is preserved. If the ensemble changes at any point before a Disconnect, Curator's ConnectionState#checkState() calls handleNewConnectionString(), which constructs a new native ZK client, discarding the previous session id, and losing all locks.
This can be expensive.
Can ConnectionState be made to preserve the session id, or be more conservative about discarding the entire native client on a Disconnected event?
An ensemble change (e.g. adding a new node to a cluster) does not mean that all session ids are now invalid. The next network glitch should not break locks.
There is no assumption in this description that the reconfiguration and the glitch/disconnection were related - they need not be.