[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-645) Different handling of max-attempts parameter on Undertow and httpd implementation

[Radoslav Husar (JIRA)]

    [ https://issues.jboss.org/browse/MODCLUSTER-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550055#comment-13550055 ] 

Radoslav Husar edited comment on MODCLUSTER-645 at 3/23/18 11:12 AM:
---------------------------------------------------------------------

There are no changes in mod_cluster for this, so converting this to a tracker for UNDERTOW-1315 and WFLY-10093. Undertow fixes the off by one problem, WildFly one fixes the incorrect descriptions.


was (Author: rhusar):
There are no changes in mod_cluster for this, so converting this to a tracker for UNDERTOW-1315 and WFLY (TBA).

> Different handling of max-attempts parameter on Undertow and httpd implementation
> ---------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-645
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-645
>             Project: mod_cluster
>          Issue Type: Task
>    Affects Versions: 1.3.5.Final
>            Reporter: Jan Kašík
>            Assignee: Radoslav Husar
>            Priority: Critical
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)