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 Fri, 04 Dec 2015 18:06:11 GMT


Paulo Motta commented on CASSANDRA-9748:

bq. One nice to have that occurred to me would be to log the interfaces we end up binding

we could do that, but why exactly? since the {{listen_address}} and {{broadcast_address}}
are explicitly defined, the admin should know which interfaces are they bound to. We would
probably need to do additional work to fetch this, so I'd prefer to keep it as is, unless
there's a good reason for it.

> Can't see other nodes when using multiple network interfaces
> ------------------------------------------------------------
>                 Key: CASSANDRA-9748
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Streaming and Messaging
>         Environment: Cassandra 2.0.16; multi-DC configuration
>            Reporter: Roman Bielik
>            Assignee: Paulo Motta
>            Priority: Minor
>              Labels: docs-impacting
>             Fix For: 2.1.x, 2.2.x, 3.0.x
>         Attachments: system_node1.log, system_node2.log
> 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