[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18200: - Fix Version/s: 4.1.1 4.0.8 4.2 (was: 4.x) (was: 4.0.x) (was: 4.1.x) Since Version: 4.0-alpha1 Source Control Link: https://github.com/apache/cassandra/commit/0b7e3a8ee7f9359eaf63208e12f32b19e6874e74 Resolution: Fixed Status: Resolved (was: Ready to Commit) Sure. Committed, thanks for the review. > 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.8, 4.1.1, 4.2 > > 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
[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18200: -- Status: Ready to Commit (was: Review In Progress) > 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
[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18200: -- Reviewers: Brandon Williams, Stefan Miklosovic (was: Brandon Williams) > 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
[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18200: -- Status: Review In Progress (was: Needs Committer) > 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
[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ 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
[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18200: - Status: Needs Committer (was: Patch Available) > 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
[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18200: - Bug Category: Parent values: Availability(12983)Level 1 values: Unavailable(12994) Complexity: Normal Discovered By: User Report Fix Version/s: 4.0.x 4.1.x 4.x Reviewers: Brandon Williams Severity: Normal Assignee: Maciej Sokol Status: Open (was: Triage Needed) > 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
[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Sokol updated CASSANDRA-18200: - Attachment: (was: patch) > 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 >Priority: Normal > 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
[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Sokol updated CASSANDRA-18200: - Attachment: patch.txt > 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 >Priority: Normal > 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
[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Sokol updated CASSANDRA-18200: - Attachment: patch > 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 >Priority: Normal > Attachments: patch > > > 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
[jira] [Updated] (CASSANDRA-18200) Cassandra messaging to self changed behavior
[ https://issues.apache.org/jira/browse/CASSANDRA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Sokol updated CASSANDRA-18200: - 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] was: 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: [https://github.com/apache/cassandra/blob/cassandra-4.0/src/java/org/apache/cassandra/net/OutboundConnectionSettings.java#L451] > 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 >Priority: Normal > > 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
