Details

      Description

      While trying to reproduce CASSANDRA-8343 I was not able to trigger a SocketTimeoutException by adding an artificial sleep longer than streaming_socket_timeout_in_ms.

      After investigation, I detected two problems:

      • ReadableByteChannel creation via socket.getChannel(), as done in ConnectionHandler.getReadChannel(socket), does not respect socket.setSoTimeout(), as explained in this blog post
        • The only difference between “blocking NIO” and “NIO wrapped around IO” is that you can’t use socket timeout with SocketChannels. Why ? Read a javadoc for setSocketTimeout(). It says that this timeout is used only by streams.

      • socketSoTimeout is never set on "follower" side, only on initiator side via DefaultConnectionFactory.createConnection(peer).

      This may cause streaming to hang indefinitely, as exemplified by CASSANDRA-8621:

      For the scenario that prompted this ticket, it appeared that the streaming process was completely stalled. One side of the stream (the sender side) had an exception that appeared to be a connection reset. The receiving side appeared to think that the connection was still active, at least in terms of the netstats reported by nodetool. We were unable to verify whether this was specifically the case in terms of connected sockets due to the fact that there were multiple streams for those peers, and there is no simple way to correlate a specific stream to a tcp session.

        Attachments

          Activity

            People

            • Assignee:
              pauloricardomg Paulo Motta
              Reporter:
              pauloricardomg Paulo Motta
              Reviewer:
              Yuki Morishita
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: