[jira] [Comment Edited] (CASSANDRA-5084) Cassandra should expose connected client state via JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786077#comment-13786077 ] Suresh edited comment on CASSANDRA-5084 at 10/4/13 11:25 AM: - Modified patch, for connection counts and session details for thrift session, is attached here was (Author: sureshsajja): Modified patch, for connection counts and session details for session details is attached here 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-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)
[jira] [Comment Edited] (CASSANDRA-5084) Cassandra should expose connected client state via JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755148#comment-13755148 ] Dave Brosius edited comment on CASSANDRA-5084 at 8/30/13 9:15 PM: -- it's just there to let the classloader do it's thing. stuff gets registered in the static block. could do a myriad of things, Class.forName(ThriftSessionManager.class.getName()); or ThriftSessionManager t = ThriftSessionManager.instance; etc, etc was (Author: dbrosius): it's just there to let the classloader do it's thing. stuff gets registered in the static block. could do a myriad of things, Class.forName(ThriftSessionManager.class.getName()); etc 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
[jira] [Comment Edited] (CASSANDRA-5084) Cassandra should expose connected client state via JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755148#comment-13755148 ] Dave Brosius edited comment on CASSANDRA-5084 at 8/30/13 9:16 PM: -- it's just there to let the classloader do it's thing. stuff gets registered in the static block. could do a myriad of things, Class.forName(ThriftSessionManager.class.getName()); or ThriftSessionManager t = ThriftSessionManager.instance; etc, etc adding a no-op ThriftSessionManager.install() method in there, and calling it would be more self documenting. i suppose. was (Author: dbrosius): it's just there to let the classloader do it's thing. stuff gets registered in the static block. could do a myriad of things, Class.forName(ThriftSessionManager.class.getName()); or ThriftSessionManager t = ThriftSessionManager.instance; etc, etc 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
