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

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

    Comment: was deleted

(was: Looking through the source I don't see how the metric could be incorrect. 
It's pretty cut and dry, just a activeSocketSessions.size(); .

Perhaps sockets are being left open erroneously :/ ?)

> 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.
> 2. Disable thrift.
> 3. Enable thrift, have the clients reconnect.
> 4. Observe netstat or lsof, and you'll find a lot of sockets in CLOSE_WAIT 
> state. 
>   * Also verifiable in 
> org.apache.cassandra.metrics:type=Client,name=connectedThriftClients MBean.



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

Reply via email to