-
Task
-
Resolution: Done
-
Critical
-
None
-
1.3.5.Final
-
None
-
None
-
Documentation (Ref Guide, User Guide, etc.), User Experience
The behavior of balancer is different on httpd in comparsion with Undertow implementation when max-attempts parameter is set.
- Undertow: max-attempts is total count of requests made by balancer in failover scenario. When max-attemps is set to 1 and target worker fails after first attempt made by balancer, no further attempts are made.
- httpd: max-attempts is count of retries made by balancer after first attempt fails. When max-attempts is set to 1 and target worker fails after first attempt made by balancer, second worker is chosen and request is sent towards it.
This doesn't seem right and I suggest to unify behavior across implementations.
- incorporates
-
UNDERTOW-1315 Undertow mod_cluster balancer retries one less time
- Resolved
-
WFLY-10093 mod_cluster "max-attempts" attribute description is incorrect
- Closed
- is related to
-
JBEAP-10145 (max-retries/max-attemps) Failover configuration issue
- Resolved
- relates to
-
UNDERTOW-1042 Disabling failover with max-attemps ignored
- Closed