Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C865E18E33 for ; Fri, 4 Dec 2015 18:01:11 +0000 (UTC) Received: (qmail 6961 invoked by uid 500); 4 Dec 2015 18:01:11 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 6915 invoked by uid 500); 4 Dec 2015 18:01:11 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 6753 invoked by uid 99); 4 Dec 2015 18:01:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2015 18:01:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2ED992C1F72 for ; Fri, 4 Dec 2015 18:01:11 +0000 (UTC) Date: Fri, 4 Dec 2015 18:01:11 +0000 (UTC) From: "Ariel Weisberg (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-9748) Can't see other nodes when using multiple network interfaces MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-9748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041871#comment-15041871 ] Ariel Weisberg commented on CASSANDRA-9748: ------------------------------------------- I am +1 on this. One nice to have that occurred to me would be to log the interfaces we end up binding on. > 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)