[ https://issues.apache.org/jira/browse/CASSANDRA-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300475#comment-15300475 ]
Paulo Motta commented on CASSANDRA-8621: ---------------------------------------- Closing this because the issue that originated this ticket was likely caused by CASSANDRA-11286 and stream sockets will no longer be idle after CASSANDRA-11841, so a closed/reset stream socket will generally mean the node is unreachable (see more details above). > For streaming operations, when a socket is closed/reset, we should > retry/reinitiate that stream > ----------------------------------------------------------------------------------------------- > > Key: CASSANDRA-8621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8621 > Project: Cassandra > Issue Type: Improvement > Components: Streaming and Messaging > Reporter: Jeremy Hanna > Assignee: Paulo Motta > > Currently we have a setting (streaming_socket_timeout_in_ms) that will > timeout and retry the stream operation in the case where tcp is idle for a > period of time. However in the case where the socket is closed or reset, we > do not retry the operation. This can happen for a number of reasons, > including when a firewall sends a reset message on a socket during a > streaming operation, such as nodetool rebuild necessarily across DCs or > repairs. > Doing a retry would make the streaming operations more resilient. It would > be good to log the retry clearly as well (with the stream session ID and node > address). -- This message was sent by Atlassian JIRA (v6.3.4#6332)