cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9748) Can't see other nodes when using multiple network interfaces
Date Wed, 16 Sep 2015 18:12:47 GMT


Paulo Motta commented on CASSANDRA-9748:

{{prefer_local}} basically makes connections in the local datacenter use {{listen_address}}
 (which is typically a private IP), instead of {{broadcast_address}} (which is typically a
public IP), but that was just a wild guess which didn't seem to work.

ok, could you try to reproduce the issue again with only 2 nodes (a seed, and a non-seed)
with version 2.1 or 2.2, and change the root level from {{INFO}} to {{DEBUG}} on {{conf/logback.xml}},
and also add the following lines to the end of your {{conf/logback.xml}} (within the configuration

<logger name="" level="TRACE"/>
<logger name="org.apache.cassandra.gms" level="TRACE"/>

Please attach the corresponding {{log/system.log}} of both nodes here so we can investigate
what's going on with more detail. Also, please attach the output of {{nodetool gossipinfo}}
of both nodes.

> 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
>            Assignee: Paulo Motta
> 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