cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5084) Cassandra should expose connected client state via JMX
Date Tue, 17 Sep 2013 14:52:54 GMT


Aleksey Yeschenko commented on CASSANDRA-5084:

I 100% agree with Dave here. Exposing the current clientstate keyspace is definitely useless,
at least in CQL3 world, where you can specify keyspace.table in almost every statement. And
user login information is mostly useless as well.

Just the session counts, as originally suggested in the issue description, will do.
> 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
>             Fix For: 1.2.10
>         Attachments: 5084-v1.txt, cassandra-1.2-5084-native.patch, trunk-5084-native.patch,
trunk-5084.patch, trunk-5084-sept4.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