[jira] [Issue Comment Deleted] (CASSANDRA-5084) Cassandra should expose connected client state via JMX

["Brandon Williams (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-5084:
----------------------------------------

    Comment: was deleted

(was: Accidentally changed the status to testing...
can somebody change it back..
)
    
> Cassandra should expose connected client state via JMX
> ------------------------------------------------------
>
>                 Key: CASSANDRA-5084
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5084
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Robert Coli
>            Assignee: Suresh
>            Priority: Minor
>              Labels: lhf
>         Attachments: trunk-5084.patch
>
>
> There is currently no good way to determine or estimate how many clients are connected to a cassandra node without using netstat or (if using sync thrift server) counting threads. There is also no way to understand what state any given connection is in. People regularly come into #cassandra/cassandra-user@ and ask how to get the equivalent of a MySQL "SHOW FULL PROCESSLIST."
> While I understand that feature parity with SHOW FULL PROCESSLIST/information_schema.processlist is unlikely, even a few basic metrics like "number of connected clients" or "number of active clients" would greatly help with this operational information need.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira