cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9748) Can't see other nodes when using multiple network interfaces
Date Fri, 04 Dec 2015 18:09:11 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041890#comment-15041890
] 

Ariel Weisberg commented on CASSANDRA-9748:
-------------------------------------------

If they specify the interface via a hostname it could end up binding to an IP other than what
you intended. Also it saves you having to open up another file. For instance if someone uploads
their log but not the yaml you won't have to go ask for the yaml. 

In that vein I've also implemented dumping the config into log files at the beginning of each
one so when someone submits a log it always has the config in it even when the log file rolls.
I'll think about suggesting that separately.

> Can't see other nodes when using multiple network interfaces
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-9748
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9748
>             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:
> http://docs.datastax.com/en/cassandra/2.0/cassandra/configuration/configMultiNetworks.html
> 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:* 0.0.0.0
> *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 0.0.0.0:7199                0.0.0.0:*                   LISTEN  
   3587/java           
> tcp        0      0 10.0.1.1:9160               0.0.0.0:*                   LISTEN  
   3587/java           
> tcp        0      0 10.0.1.1:9042               0.0.0.0:*                   LISTEN  
   3587/java           
> tcp        0      0 10.0.1.1:7000               0.0.0.0:*                   LISTEN  
   3587/java           
> tcp        0      0 127.0.0.1:7199              127.0.0.1:52874             ESTABLISHED
3587/java           
> tcp        0      0 10.0.1.1:7199               10.0.1.1:39650              ESTABLISHED
3587/java 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message