You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Vijay (Created) (JIRA)" <ji...@apache.org> on 2012/02/06 21:43:59 UTC
[jira] [Created] (CASSANDRA-3867) Disablethrift and Enablethrift
can leaves behind zombie connections on THSHA server
Disablethrift and Enablethrift can leaves behind zombie connections on THSHA server
-----------------------------------------------------------------------------------
Key: CASSANDRA-3867
URL: https://issues.apache.org/jira/browse/CASSANDRA-3867
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.7
Reporter: Vijay
Assignee: Vijay
Fix For: 1.0.8
While doing nodetool disable thrift we disable selecting threads and close them... but the connections are still active...
Enable thrift creates a new Selector threads because we create new ThriftServer() which will cause the old connections to be zombies.
I think the right fix will be to call server.interrupt(); and then close the connections when they are done selecting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3867) Disablethrift and Enablethrift
can leaves behind zombie connections on THSHA server
Posted by "Brandon Williams (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206971#comment-13206971 ]
Brandon Williams commented on CASSANDRA-3867:
---------------------------------------------
+1
> Disablethrift and Enablethrift can leaves behind zombie connections on THSHA server
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-3867
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3867
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.7
> Reporter: Vijay
> Assignee: Vijay
> Fix For: 1.0.8
>
> Attachments: 0001-CASSANDRA-3867.patch
>
>
> While doing nodetool disable thrift we disable selecting threads and close them... but the connections are still active...
> Enable thrift creates a new Selector threads because we create new ThriftServer() which will cause the old connections to be zombies.
> I think the right fix will be to call server.interrupt(); and then close the connections when they are done selecting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3867) Disablethrift and Enablethrift
can leaves behind zombie connections on THSHA server
Posted by "Vijay (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vijay updated CASSANDRA-3867:
-----------------------------
Attachment: 0001-CASSANDRA-3867.patch
Simple patch to close the selector when disablethrift.
> Disablethrift and Enablethrift can leaves behind zombie connections on THSHA server
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-3867
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3867
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.7
> Reporter: Vijay
> Assignee: Vijay
> Fix For: 1.0.8
>
> Attachments: 0001-CASSANDRA-3867.patch
>
>
> While doing nodetool disable thrift we disable selecting threads and close them... but the connections are still active...
> Enable thrift creates a new Selector threads because we create new ThriftServer() which will cause the old connections to be zombies.
> I think the right fix will be to call server.interrupt(); and then close the connections when they are done selecting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira