[
https://issues.apache.org/jira/browse/CASSANDRA-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Stepura updated CASSANDRA-5084:
---------------------------------------
Attachment: cassandra-1.2-5084-metrics-v2.patch
New version of the patch
* Singleton instance of {{ClientMetrics}} object
* Each server registers its connections counter in that instance
Also added a comment for a logic around {{allChannels.size()}}
> 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
> Fix For: 1.2.11
>
> Attachments: 5084_thrift_V2.patch, 5084-v1.txt,
> cassandra-1.2-5084-metrics.patch, cassandra-1.2-5084-metrics-v2.patch,
> 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 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 was sent by Atlassian JIRA
(v6.1#6144)
