-
Bug
-
Resolution: Done
-
Major
-
1.2.13.Final, 1.3.5.Final
-
None
Under the following conditions:
1. A request arrives for a session with an unknown route
2. A request arrives for a session with a known route in an error state, or if the intended worker is unresponsive and needs to failover
... the failover target must be chosen in a deterministic way. This is meant to mitigate the situation where concurrent requests failover to different nodes and cause cluster-wide contention for the session. Given a consistent ordering of workers (e.g. lexographically), the failover target should be chosen by something like: hash code of session id % active worker count.
- is cloned by
-
UNDERTOW-898 Failover targets should be chosen deterministically
- Resolved
- is related to
-
JBEAP-8550 Deterministic failover session owner issue
- Closed
-
MODCLUSTER-557 Hot standby workers should be excluded from the deterministic failover candidate list
- Open