...
- Treat SUSPENDED as a complete connection loss. This will cause more instability in your application but is the safest option
- Use Curator's default session simulation which uses an internal timer of 100% of the negotiated session timeout - this is the default in Curator since 3.x
- If your application demands it, you can instruct Curator's session timer to use 33% of the session timeout (see below). Note: this assumes that connection loses losses are the result of missed heartbeats with the server which isn't always the case.
...