Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 429DB10C1B for ; Sun, 1 Sep 2013 02:46:58 +0000 (UTC) Received: (qmail 54744 invoked by uid 500); 1 Sep 2013 02:46:58 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 54692 invoked by uid 500); 1 Sep 2013 02:46:57 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 54670 invoked by uid 99); 1 Sep 2013 02:46:55 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Sep 2013 02:46:55 +0000 Date: Sun, 1 Sep 2013 02:46:55 +0000 (UTC) From: "Mikhail Stepura (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-5084) Cassandra should expose connected client state via JMX MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Stepura updated CASSANDRA-5084: --------------------------------------- Attachment: trunk-5084-native.patch Patch for the native interface. Exported {{ConnectionsCount}} attribute and {{listConnections}} operation via JMX > 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-native.patch, 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