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 0DF63181AA for ; Fri, 18 Mar 2016 13:07:34 +0000 (UTC) Received: (qmail 46093 invoked by uid 500); 18 Mar 2016 13:07:33 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 46056 invoked by uid 500); 18 Mar 2016 13:07:33 -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 46045 invoked by uid 99); 18 Mar 2016 13:07:33 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Mar 2016 13:07:33 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 72C2D2C1F5D for ; Fri, 18 Mar 2016 13:07:33 +0000 (UTC) Date: Fri, 18 Mar 2016 13:07:33 +0000 (UTC) From: "Branimir Lambov (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-11332) nodes connect to themselves when NTS is used 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-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Branimir Lambov updated CASSANDRA-11332: ---------------------------------------- Status: Patch Available (was: Open) Patch adding local address to {{PropertyFileSnitch}}: |[code trunk|https://github.com/blambov/cassandra/tree/11332]|[utest |http://cassci.datastax.com/job/blambov-11332-testall/]|[dtest|http://cassci.datastax.com/job/blambov-9421-dtest/]| This is an LHF-hackathon fix to the concrete problem, I think we should consider a more thorough investigation of where and how we use local addresses in token/rack/dc/etc. lookups. > nodes connect to themselves when NTS is used > -------------------------------------------- > > Key: CASSANDRA-11332 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11332 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Brandon Williams > Assignee: Branimir Lambov > Fix For: 2.1.x > > > I tested this with both the simple snitch and PFS. It's quite easy to repro, setup a cluster, start it. Mine looks like this: > {noformat} > tcp 0 0 10.208.8.123:48003 10.208.8.63:7000 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:7000 10.208.8.63:40215 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:55559 10.208.35.225:7000 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:33498 10.208.8.63:7000 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:7000 10.208.35.225:52530 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:7000 10.208.35.225:53674 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:40846 10.208.35.225:7000 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:7000 10.208.8.63:48880 ESTABLISHED 26254/java > {noformat} > No problems so far. Now create a keyspace using NTS with an rf of 3, and perform some writes. Now it looks like this: > {noformat} > tcp 0 0 10.208.8.123:48003 10.208.8.63:7000 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:7000 10.208.8.123:35024 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:35024 10.208.8.123:7000 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:47212 10.208.8.123:7000 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:7000 10.208.8.63:40215 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:55559 10.208.35.225:7000 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:33498 10.208.8.63:7000 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:7000 10.208.35.225:52530 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:7000 10.208.35.225:53674 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:7000 10.208.8.123:47212 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:40846 10.208.35.225:7000 ESTABLISHED 26254/java > tcp 0 0 10.208.8.123:7000 10.208.8.63:48880 ESTABLISHED 26254/java > {noformat} > I can't think of any reason for a node to connect to itself, and this can cause problems with PFS where you might only define the broadcast addresses, but now you need the internal addresses too because the node will need to look itself up when connecting to itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)