[jboss-jira] [JBoss JIRA] (WFLY-8304) mod_cluster max-attempts minimal value

Jan Stefl (JIRA) issues at jboss.org
Fri Aug 11 07:20:02 EDT 2017


     [ https://issues.jboss.org/browse/WFLY-8304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Stefl updated WFLY-8304:
----------------------------
    Tester: Jan Kašík  (was: Bogdan Sikora)


> mod_cluster max-attempts minimal value
> --------------------------------------
>
>                 Key: WFLY-8304
>                 URL: https://issues.jboss.org/browse/WFLY-8304
>             Project: WildFly
>          Issue Type: Bug
>          Components: mod_cluster
>    Affects Versions: 10.1.0.Final
>            Reporter: Bogdan Sikora
>            Assignee: Radoslav Husar
>            Priority: Minor
>             Fix For: 11.0.0.Alpha1
>
>
> [Documentation|http://modcluster.io/documentation/#proxy-configuration-1]
> {noformat}
> Maximum number of failover attempts before giving up. The minimum value is 0, i.e. no failover. The default value is 1, i.e. do a one failover attempt.
> {noformat}
> Max-attemps minimal value is
> {noformat}
> "max-attempts" => {
>                 "type" => INT,
>                 "description" => "Max attempts to process an idempotent request.",
>                 "expressions-allowed" => true,
>                 "nillable" => true,
>                 "default" => 1,
>                 "min" => -1L,
>                 "max" => 2147483647L,
>                 "access-type" => "read-write",
>                 "storage" => "configuration",
>                 "restart-required" => "all-services"
>             },
> {noformat}
> Min value to 0. In the mod_cluster subsystem(worker side). 
> And max-attemps handling on the balancer side. Balancer has minimal value of 1 and therefore any value lower than that is ignored. Should be 0.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)



More information about the jboss-jira mailing list