Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-5084

Cassandra should expose connected client state via JMX

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Fix Version/s: 1.2.11
    • Component/s: None
    • Labels:

      Description

      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.

        Attachments

        1. trunk-5084-sept4.patch
          7 kB
          Suresh
        2. trunk-5084-native.patch
          6 kB
          Mikhail Stepura
        3. trunk-5084.patch
          6 kB
          Suresh
        4. cassandra-1.2-5084-native.patch
          6 kB
          Mikhail Stepura
        5. cassandra-1.2-5084-metrics-v2.patch
          7 kB
          Mikhail Stepura
        6. cassandra-1.2-5084-metrics.patch
          4 kB
          Mikhail Stepura
        7. 5084-v1.txt
          6 kB
          Brandon Williams
        8. 5084_thrift_V2.patch
          5 kB
          Suresh

          Activity

            People

            • Assignee:
              mishail Mikhail Stepura
              Reporter:
              rcoli Robert Coli
              Reviewer:
              Jonathan Ellis
            • Votes:
              8 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: