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] [Updated] (CASSANDRA-6546) disablethrift followed by enablethrift results in unclosed file descriptors
Date Fri, 03 Jan 2014 13:40:52 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Harvey updated CASSANDRA-6546:
------------------------------------

    Description: 
Updated bug title to reflect what is actually happening. Disabling thrift and then re-enabling
thrift results in unclosed thrift sockets being left around.


Steps to reproduce:

1. Have a handful of clients connect via thrift.
1. Disable thrift.
1. Enable thrift, have the clients reconnect.
1. Observe netstat or lsof, and you'll find a lot of sockets in CLOSE_WAIT state.


  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
>
> Updated bug title to reflect what is actually happening. Disabling thrift and then re-enabling
thrift results in unclosed thrift sockets being left around.
> Steps to reproduce:
> 1. Have a handful of clients connect via thrift.
> 1. Disable thrift.
> 1. Enable thrift, have the clients reconnect.
> 1. Observe netstat or lsof, and you'll find a lot of sockets in CLOSE_WAIT state.



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

Mime
View raw message