You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jason Harvey (JIRA)" <ji...@apache.org> on 2014/01/03 14:36:50 UTC
[jira] [Updated] (CASSANDRA-6546) disablethrift followed by
enablethrift results in unclosed file descriptors
[ https://issues.apache.org/jira/browse/CASSANDRA-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Harvey updated CASSANDRA-6546:
------------------------------------
Description:
-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 ).-
was:
-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 ).-
> disablethrift followed by enablethrift results in unclosed file descriptors
> ---------------------------------------------------------------------------
>
> 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)