cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Bielik (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9748) Can't see other nodes when using multiple network interfaces
Date Tue, 15 Sep 2015 11:59:45 GMT


Roman Bielik commented on CASSANDRA-9748:

I have retested on Cassandra 2.2.1 and the results are pretty much the same.
If my premise is correct, I need to use public_IP as seeds as this is the interface/network
where different datacenters can connect to each other.

I have tested all possible permutations of listen_address, broadcast_address and broadcast_rpc_address.
The seeds were set to public IP and rpc_address to in all tests.

listen_address - if set to private_IP, the ring showed only one node
broadcast_address - if set to private_IP, there was always problem with gossip
broadcast_rpc_address - it did not matter in terms of connection or ring, so I could use private
IP here.

To sum up: I still needed to use public IP in seeds, listen_address and broadcast_address
in order to start a Cassandra cluster.

> Can't see other nodes when using multiple network interfaces
> ------------------------------------------------------------
>                 Key: CASSANDRA-9748
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra 2.0.16; multi-DC configuration
>            Reporter: Roman Bielik
> The idea is to setup a multi-DC environment across 2 different networks based on the
following configuration recommendations:
> Each node has 2 network interfaces. One used as a private network (DC1: 10.0.1.x and
DC2: 10.0.2.x). The second one a "public" network where all nodes can see each other (this
one has a higher latency). 
> Using the following settings in cassandra.yaml:
> *seeds:* public IP (same as used in broadcast_address)
> *listen_address:* private IP
> *broadcast_address:* public IP
> *rpc_address:*
> *endpoint_snitch:* GossipingPropertyFileSnitch
> _(tried different combinations with no luck)_
> No firewall and no SSL/encryption used.
> The problem is that nodes do not see each other (a gossip problem I guess). The nodetool
ring/status shows only the local node but not the other ones (even from the same DC).
> When I set listen_address to public IP, then everything works fine, but that is not the
required configuration.
> _Note: Not using EC2 cloud!_
> netstat -anp | grep -E "(7199|9160|9042|7000)"
> tcp        0      0      *                   LISTEN  
> tcp        0      0     *                   LISTEN  
> tcp        0      0     *                   LISTEN  
> tcp        0      0     *                   LISTEN  
> tcp        0      0                 ESTABLISHED
> tcp        0      0                   ESTABLISHED

This message was sent by Atlassian JIRA

View raw message