cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Harvey (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-6546) connectedThriftClients metric appears to be incorrect after thrift stop/start
Date Fri, 03 Jan 2014 13:24:50 GMT
Jason Harvey created CASSANDRA-6546:
---------------------------------------

             Summary: connectedThriftClients metric appears to be incorrect after thrift stop/start
                 Key: CASSANDRA-6546
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6546
             Project: Cassandra
          Issue Type: Bug
            Reporter: Jason Harvey
            Priority: Minor


Disabling and then re-enabling thrift resulted in this stat reporting double the number of
connected sockets on the service.

Alternatively, if the metric is accurate, then disabling and then re-enabling thrift may be
resulting in a bunch of unused FDs?

Reproducing is easy. Have a handful of thrift clients, disablethrift, wait a few minutes,
re-enable thrift, have your client apps reconnect, then compare actual connected sockets (via
netstat or lsof or what have you) to the value from this MBean ( org.apache.cassandra.metrics:type=Client,name=connectedThriftClients
).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message