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

OutboundTcpConnectionPool should route messages to sockets by size not type




      I was looking at this trying to understand what messages flow over which connection.

      For reads the request goes out over the command connection and the response comes back over the ack connection.

      For writes the request goes out over the command connection and the response comes back over the command connection.

      Reads get a dedicated socket for responses. Mutation commands and responses both travel over the same socket along with read requests.

      Sockets are used uni-directional so there are actually four sockets in play and four threads at each node (2 inbounded, 2 outbound).

      CASSANDRA-488 doesn't leave a record of what the impact of this change was. If someone remembers what situations were made better it would be good to know.

      I am not clear on when/how this is helpful. The consumer side shouldn't be blocking so the only head of line blocking issue is the time it takes to transfer data over the wire.

      If message size is the cause of blocking issues then the current design mixes small messages and large messages on the same connection retaining the head of line blocking.

      Read requests share the same connection as write requests (which are large), and write acknowledgments (which are small) share the same connections as write requests. The only winner is read acknowledgements.


        1. 8789.diff
          25 kB
          Ariel Weisberg



            aweisberg Ariel Weisberg
            aweisberg Ariel Weisberg
            Ariel Weisberg
            Benedict Elliott Smith
            0 Vote for this issue
            11 Start watching this issue