[
https://issues.apache.org/jira/browse/CASSANDRA-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Yeksigian updated CASSANDRA-11332:
---------------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.1.x)
3.10
3.0.9
2.2.8
Status: Resolved (was: Patch Available)
+1
Committed as
[ad4a91da7|http://git-wip-us.apache.org/repos/asf/cassandra/commit/ad4a91da7].
I didn't put this into 2.1 as it doesn't seem like a critical fix, but did put
it into 2.2+.
> nodes connect to themselves when NTS is used
> --------------------------------------------
>
> Key: CASSANDRA-11332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11332
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Brandon Williams
> Assignee: Branimir Lambov
> Fix For: 2.2.8, 3.0.9, 3.10
>
>
> I tested this with both the simple snitch and PFS. It's quite easy to repro,
> setup a cluster, start it. Mine looks like this:
> {noformat}
> tcp 0 0 10.208.8.123:48003 10.208.8.63:7000
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:7000 10.208.8.63:40215
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:55559 10.208.35.225:7000
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:33498 10.208.8.63:7000
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:7000 10.208.35.225:52530
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:7000 10.208.35.225:53674
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:40846 10.208.35.225:7000
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:7000 10.208.8.63:48880
> ESTABLISHED 26254/java
> {noformat}
> No problems so far. Now create a keyspace using NTS with an rf of 3, and
> perform some writes. Now it looks like this:
> {noformat}
> tcp 0 0 10.208.8.123:48003 10.208.8.63:7000
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:7000 10.208.8.123:35024
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:35024 10.208.8.123:7000
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:47212 10.208.8.123:7000
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:7000 10.208.8.63:40215
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:55559 10.208.35.225:7000
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:33498 10.208.8.63:7000
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:7000 10.208.35.225:52530
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:7000 10.208.35.225:53674
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:7000 10.208.8.123:47212
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:40846 10.208.35.225:7000
> ESTABLISHED 26254/java
> tcp 0 0 10.208.8.123:7000 10.208.8.63:48880
> ESTABLISHED 26254/java
> {noformat}
> I can't think of any reason for a node to connect to itself, and this can
> cause problems with PFS where you might only define the broadcast addresses,
> but now you need the internal addresses too because the node will need to
> look itself up when connecting to itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
