[jboss-jira] [JBoss JIRA] (WFLY-5002) Undertow mod_cluster CLI: Display node's Flushpackets, Flushwait, Ping, Smax and Ttl properties

Stuart Douglas (JIRA) issues at jboss.org
Fri Jul 24 00:20:06 EDT 2015


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

Stuart Douglas moved UNDERTOW-494 to WFLY-5002:
-----------------------------------------------

              Project: WildFly  (was: Undertow)
                  Key: WFLY-5002  (was: UNDERTOW-494)
           Issue Type: Feature Request  (was: Bug)
    Affects Version/s:     (was: 1.3.0.Beta3)
          Component/s: Web (Undertow)
                           (was: Proxy)


> Undertow mod_cluster CLI: Display node's Flushpackets, Flushwait, Ping, Smax and Ttl properties
> -----------------------------------------------------------------------------------------------
>
>                 Key: WFLY-5002
>                 URL: https://issues.jboss.org/browse/WFLY-5002
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Web (Undertow)
>            Reporter: Michal Karm Babacek
>            Assignee: Stuart Douglas
>              Labels: mod_cluster
>
> As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities.
> h3. Display node's Flushpackets, Flushwait, Ping, Smax and Ttl properties
> At the moment, this is all there is to see:
> {noformat}
> "balancer" => {
>     "qa_balancer" => {"node" => {"worker-2" => {
>         "load" => 89,
>         "status" => "NODE_UP",
>         "context" => {"/clusterbench" => {
>             "requests" => 0,
>             "status" => "enabled"
>         }}
>     }}},
> ...
> {noformat}
> h3. Call to action
> For any serious enterprise deployment, users need to tweak at least ping and ttl attributes and they will need to be able to see their values on Undertow mod_cluster proxy balancer CLI console per each worker.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jboss-jira mailing list