-
Bug
-
Resolution: Done
-
Minor
-
None
As a follow up to JBEAP-215, this bug report is a member of a series addressing CLI management capabilities. It is of Minor priority though.
Display balancer's stickySession, stickySessionRemove, stickySessionForce, waitWorker and maxattempts properties
At the moment, this is all there is to see as far as balancer runtime configuration goes:
"balancer" => { "qa_balancer" => {"node" => {"worker-2" => { "load" => 89, "status" => "NODE_UP", "context" => {"/clusterbench" => { "requests" => 0, "status" => "enabled" }} }}}, ...
Call to action
Display runtime configuration properties for each balancer; especially these concerning session stickiness. It would help users debug their complex highly available environments without having to dauntingly parse DEBUG logs.
- clones
-
JBEAP-477 Undertow mod_cluster CLI: Display balancer's stickySession, stickySessionRemove, stickySessionForce, waitWorker and maxattempts properties
- Closed
- is related to
-
UNDERTOW-452 Undertow mod_cluster proxy does not offer any management capabilities
- Closed