[jira] [Comment Edited] (CASSANDRA-6546) disablethrift results in unclosed file descriptors

["Mikhail Stepura (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985953#comment-13985953 ] 

Mikhail Stepura edited comment on CASSANDRA-6546 at 4/30/14 7:27 PM:
---------------------------------------------------------------------

For some reason {{ThriftSessionManager.connectionComplete(SocketAddress)}} is never called in this case.
{code}
mstepura-mac:logs mikhail$ lsof -p 84299 | grep CLOSE_WAIT | wc -l
     150
{code}
And all those 150 connections are still sitting in ThriftSessionManager

!2014-04-30 12-22-17.png!
!2014-04-30 12-22-58.png!


was (Author: mishail):
For some reason {{ThriftSessionManager.connectionComplete(SocketAddress)}} is never called in this case.
{code}
mstepura-mac:logs mikhail$ lsof -p 84299 | grep CLOSE_WAIT | wc -l
     150
{code}
And all those 150 connections are still sitting in ThriftSessionManager


> disablethrift 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
>            Assignee: Mikhail Stepura
>            Priority: Minor
>         Attachments: 2014-04-30 12-22-17.png, 2014-04-30 12-22-58.png
>
>
> Disabling thrift results in unclosed thrift sockets being left around.
> Steps to reproduce and observe:
> 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 thrift sockets in CLOSE_WAIT state, and they'll never go away.
>   * Also verifiable from org.apache.cassandra.metrics:type=Client,name=connectedThriftClients MBean.
> What's extra fun about this is the leaked sockets still count towards your maximum RPC thread count. As a result, toggling thrift enough times will result in an rpc_max_threads number of CLOSED_WAIT sockets, with no new clients able to connect.
> This was reproduced with HSHA. I haven't tried it in sync yet.



--
This message was sent by Atlassian JIRA
(v6.2#6252)