cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paulo Motta <pauloricard...@gmail.com>
Subject Re: Multiple Network Interfaces in non-EC2
Date Mon, 12 Sep 2016 13:22:48 GMT
This seems like a bug, it seems we always bind the outgoing socket to the
private/listen address. Would you mind opening a JIRA and posting the link
here?

Thanks

2016-09-12 3:35 GMT-03:00 Amir Dafny-Man <A.DafnyMan@f5.com>:

> Hi,
>
>
>
> I followed the docs (http://docs.datastax.com/en/cassandra/3.x/cassandra/
> configuration/configMultiNetworks.html) and I am familiar with
> https://issues.apache.org/jira/browse/CASSANDRA-9748.
>
> Trying to establish a single 2 nodes, single DC setup. I tried Cassandra
> 3.7 but also 2.2.7.
>
> My setup:
>
> RHEL6 distribution
>
> Node1 external: 10.240.33.241
>
> Node1 internal: 192.168.33.241
>
> Node2 external: 10.240.33.244
>
> Node2 internal: 192.168.33.244
>
>
>
> cassandra-rackdc.properties (for both nodes) also tried with
> prefer_local=false:
>
> dc=vdra015-xs-15
>
> rack=rack1
>
> prefer_local=true
>
>
>
> Cassandra.yaml (changes over default):
>
> seeds: “10.240.33.241”
>
> listen_address: 192.168.33.241 or 192.168.33.244
>
> broadcast_address: 10.240.33.241 or 10.240.33.244
>
> listen_on_broadcast_address: true
>
> rpc_address: 192.168.33.241 or 192.168.33.244
>
> endpoint_snitch: GossipingPropertyFileSnitch
>
>
>
> Routing table:
>
> # ip r
>
> 192.168.33.0/24 dev eth1  proto kernel  scope link  src 192.168.33.241
>
> 10.1.21.0/24 dev eth2  proto kernel  scope link  src 10.1.21.241
>
> 10.1.22.0/24 dev eth3  proto kernel  scope link  src 10.1.22.241
>
> 10.1.23.0/24 dev eth4  proto kernel  scope link  src 10.1.23.241
>
> 10.240.32.0/21 dev eth0  proto kernel  scope link  src 10.240.33.241
>
> default via 10.240.32.1 dev eth0
>
>
>
> Experienced behavior:
>
> 1.       Node1 starts up normally
>
> # netstat -anlp|grep java
>
> tcp        0      0 127.0.0.1:55452             0.0.0.0:*
> LISTEN      10036/java
>
> tcp        0      0 127.0.0.1:7199              0.0.0.0:*
> LISTEN      10036/java
>
> tcp        0      0 10.240.33.241:7000          0.0.0.0:*
> LISTEN      10036/java
>
> tcp        0      0 192.168.33.241:7000         0.0.0.0:*
> LISTEN      10036/java
>
> tcp        0      0 ::ffff:192.168.33.241:9042
> :::*                        LISTEN      10036/java
>
> 2.       When I try to start node2, it is unable to connect to node1 IP
> set in seeds
>
> Exception (java.lang.RuntimeException) encountered during startup: Unable
> to gossip with any seeds
>
> java.lang.RuntimeException: Unable to gossip with any seeds
>
> 3.       Running tcpdumpon node2, I can see that node2 is trying to
> connect to node1 external IP but with its source internal IP
>
> # tcpdump -nn -i eth0 port 7000
>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>
> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
>
> 09:29:05.239026 IP 192.168.33.244.52900 > 10.240.33.241.7000: Flags [S],
> seq 77957108, win 14600, options [mss 1460,sackOK,TS val 65015480 ecr
> 0,nop,wscale 9], length 0
>
> 09:29:06.238188 IP 192.168.33.244.52900 > 10.240.33.241.7000: Flags [S],
> seq 77957108, win 14600, options [mss 1460,sackOK,TS val 65016480 ecr
> 0,nop,wscale 9], length 0
>
> 09:29:08.238159 IP 192.168.33.244.52900 > 10.240.33.241.7000: Flags [S],
> seq 77957108, win 14600, options [mss 1460,sackOK,TS val 65018480 ecr
> 0,nop,wscale 9], length 0
>
> 09:29:12.238129 IP 192.168.33.244.52900 > 10.240.33.241.7000: Flags [S],
> seq 77957108, win 14600, options [mss 1460,sackOK,TS val 65022480 ecr
> 0,nop,wscale 9], length 0
>
> 09:29:20.238129 IP 192.168.33.244.52900 > 10.240.33.241.7000: Flags [S],
> seq 77957108, win 14600, options [mss 1460,sackOK,TS val 65030480 ecr
> 0,nop,wscale 9], length 0
>
> 09:29:36.238161 IP 192.168.33.244.52900 > 10.240.33.241.7000: Flags [S],
> seq 77957108, win 14600, options [mss 1460,sackOK,TS val 65046480 ecr
> 0,nop,wscale 9], length 0
>
> 4.       Running tcpdump on node1, shows packets are not arriving
>
>
>
> Is something configured wrong or is this a bug?
>
>
>
> Thanks,
>
> *Amir*
>
>
>

Mime
View raw message