[CASSANDRA-18200] Cassandra messaging to self changed behavior

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0.8, 4.1.1, 5.0-alpha1, 5.0
• Component/s: Messaging/Internode
• Bug Category: Availability - Unavailable
• Severity: Normal
• Complexity: Normal
• Discovered By: User Report
• Platform: All
• Since Version: 4.0-alpha1

Source Control Link

https://github.com/apache/cassandra/commit/0b7e3a8ee7f9359eaf63208e12f32b19e6874e74

Test and Documentation Plan

run CI

• Assignee: Maciej Sokol
• Reporter: Maciej Sokol

Authors

Maciej Sokol

Reviewers

Brandon Williams, Stefan Miklosovic

• Created: 26/Jan/23 06:59
• Updated: 12/Sep/23 13:03
• Resolved: 30/Jan/23 13:08

Description

During testing of Cassandra on AWS, we noticed some behavior changes between Cassandra 3.11 and Cassandra 4.0 when it comes to messaging.
When performing a range query with consistency local_quorum, Cassandra sents a request to itself and some peers.
In case of Cassandra 4.0, it's trying to connect to itself using the broadcast_address while in Cassandra 3.11 it's connecting using the local address (see https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/net/OutboundTcpConnectionPool.java#L152.

This translation seems to be missing in Cassandra 4.X. I think the best place to fix it would be here (see attached file): https://github.com/apache/cassandra/blob/cassandra-4.0/src/java/org/apache/cassandra/net/OutboundConnectionSettings.java#L451