[CASSANDRA-14485] Optimize internode messaging protocol

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Legacy/Streaming and Messaging
• Assignee: Jason Brown
• Reporter: Jason Brown

Authors

Jason Brown

Reviewers

Dinesh Joshi

• Created: 31/May/18 16:25
• Updated: 15/May/20 08:03
• Resolved: 25/Jun/18 13:43

Description

There's some dead wood and places for optimization in the internode messaging protocol. Currently, we include the sender's IPAddressAndPort in every internode message, even though we already sent that in the handshake that established the connection/session. Further, there are several places where we can use vints instead of a fixed, 4-byte integer value- especially as those values will almost always be less than one byte.

Issue Links

• depends upon: CASSANDRA-14540 Internode messaging handshake sends wrong messaging version number
• is depended upon by: CASSANDRA-13628 switch peer-to-peer networking to non-blocking I/O via netty