[jboss-jira] [JBoss JIRA] (WFLY-8654) mod_cluster stop/stop-context(waittime=..) attribute description is wrong

[Radoslav Husar (JIRA)]

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

Radoslav Husar updated WFLY-8654:
---------------------------------
    Summary: mod_cluster stop/stop-context(waittime=..) attribute description is wrong  (was: Improve mod_cluster stop/stop-context(waittime=..) attribute description)


> mod_cluster stop/stop-context(waittime=..) attribute description is wrong
> -------------------------------------------------------------------------
>
>                 Key: WFLY-8654
>                 URL: https://issues.jboss.org/browse/WFLY-8654
>             Project: WildFly
>          Issue Type: Bug
>          Components: mod_cluster
>    Affects Versions: 11.0.0.Alpha1
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>            Priority: Minor
>
> Cli operation description
> {noformat}
> [standalone at localhost:9990 /] /subsystem=modcluster/:read-operation-description(name=stop
> {
>     "outcome" => "success",
>     "result" => {
>         "operation-name" => "stop",
>         "description" => "Tell reverse proxies that all contexts on the node can't process requests.",
>         "request-properties" => {"waittime" => {
>             "type" => INT,
>             "description" => "Timeout to wait for all contexts to stop.",
>             "expressions-allowed" => false,
>             "required" => false,
>             "nillable" => true,
>             "default" => 10,
>             "unit" => "SECONDS"
>         }},
>         "reply-properties" => {},
>         "read-only" => false,
>         "runtime-only" => true
>     }
> }
> {noformat}
> Documentation
> {noformat}
>  Stopping a context with waittime set to 0, meaning no timeout, instructs the balancer to stop routing any request to it immediately, which forces failover to another available context.
> If you set a timeout value using the waittime argument, no new sessions are created on this context, but existing sessions will continue to be directed to this node until they complete or the specified timeout has elapsed. The waittime argument defaults to 10 seconds. 
> {noformat}
> There is difference, documentation basically says that till timeout is hit, node is disabled, cli description isn't that specific. Could you elaborate this?



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