[jira] [Created] (CASSANDRA-8621) For streaming operations, when a socket is closed/reset, we should retry/reinitiate that stream

["Jeremy Hanna (JIRA)" <ji...@apache.org>]

Jeremy Hanna created CASSANDRA-8621:
---------------------------------------

             Summary: 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: Core
            Reporter: Jeremy Hanna


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 - think 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).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)