[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-18200: ----------------------------------------- Test and Documentation Plan: run CI Status: Patch Available (was: Open) > Cassandra messaging to self changed behavior > -------------------------------------------- > > Key: CASSANDRA-18200 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18200 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Internode > Reporter: Maciej Sokol > Assignee: Maciej Sokol > Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > Attachments: patch.txt > > > 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] -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org