Otherwise, at least for LeaderLatch, we lose the advantage to have the distinguish between ConnectionLossException and SessionExpiredExpection. Session expired is only generated when the client successfully reconnects to the cluster. It’s not really a very useful bit of information. Theoretically, you could assume you are still leader during SUSPENDED if the session timeout hasn’t elapsed. But, this is really trying to be too clever IMO.
-JZ
