Hi all, I'm observing an unusual ZooKeeper client behavior and wanted to confirm if it's expected.
Is it possible for a ZooKeeper client to receive the following sequence for the same session ID? (KeeperState:Disconnected → KeeperState:Expired → KeeperState:Closed → KeeperState:SyncConnected) I was under the impression that once KeeperState.Expired is received, the session is considered dead and cannot be revived. But in my logs, it looks like the client reuses the same session ID even after getting the Expired event. Has anyone else seen this behavior? Thanks, Pratyush
