Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-8621

For streaming operations, when a socket is closed/reset, we should retry/reinitiate that stream

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Won't Fix
    • Fix Version/s: None
    • Labels:
      None

      Description

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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jeromatron Jeremy Hanna
              • Votes:
                9 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: