IncomingTcpConnection can not be closed when the peer is brutaly terminated or
switch is failed
-----------------------------------------------------------------------------------------------
Key: CASSANDRA-4053
URL: https://issues.apache.org/jira/browse/CASSANDRA-4053
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.8
Reporter: Zhu Han
IncomingTcpConnection has no way to detect the peer is down when the peer meets
power loss or the network infrastructure is failed, and the thread is leaked...
For safety, as least SO_KEEPALIVE should be set on those
IncomingTcpConnections. The better way is to close the incoming connections
when failure detector notifies the peer failure, but it requires some extra
bookmarking.
Besides it, it would be better if IncomingTcpConnection and
OutgoingTcpConnection is marked as daemon thread...
--
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
