-
Bug
-
Resolution: Done
-
Minor
-
7.1.0.DR16
-
None
-
User Experience
-
-
-
-
-
Cli operation description
[standalone@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 } }
Documentation
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.
There is difference, documentation basically says that till timeout is hit, node is disabled, cli description isn't that specific. Could you elaborate this?
- is cloned by
-
WFLY-8654 mod_cluster stop/stop-context(waittime=..) attribute description is wrong
- Closed
- is related to
-
JBEAP-10821 mod_cluster stop/stop-context operations do not send STOP-* in when session draining was unsuccessful
- Closed
- relates to
-
JBEAP-10354 stop-context/stop waittime ignored
- Closed
-
JBEAP-10822 mod_cluster session draining with non-positive timeout may wait indefinitely
- Closed
-
JBEAP-10824 stop-context/stop session creation
- Closed