cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5084) Cassandra should expose connected client state via JMX
Date Sun, 04 Aug 2013 14:13:49 GMT


Suresh commented on CASSANDRA-5084:

For JMX name, I could think as org.apache.cassandra.Client:type=ClientSessionManager. 

I meant to expose the number of connected clients and their socket details. This number include
idle/active connections. It makes sense to rename the attributes as NoOfConnectedClients,

I think there will not be any concern exposing user Yes, probably we can extend this Mbean
for other operations(kill specific users by admin) later

Other programing concerns are addressed. 
> Cassandra should expose connected client state via JMX
> ------------------------------------------------------
>                 Key: CASSANDRA-5084
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Robert Coli
>            Assignee: Suresh
>            Priority: Minor
>              Labels: lhf
>         Attachments: 5084-trunk.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
> 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:

View raw message