Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 13 Feb 2014 23:18:22 +0000 (UTC)
From: "Minh Do (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12695102.1392333443114.39613.1392333502547@arcas>
In-Reply-To: <JIRA.12695102.1392333443114@arcas>
References: <JIRA.12695102.1392333443114@arcas>
Subject: [jira] [Created] (CASSANDRA-6702) Upgrading node uses the wrong
 port in gossiping
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Minh Do created CASSANDRA-6702:
----------------------------------

             Summary: Upgrading node uses the wrong port in gossiping
                 Key: CASSANDRA-6702
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6702
             Project: Cassandra
          Issue Type: Bug
          Components: Core
         Environment: 1.1.7, AWS, Ec2MultiRegionSnitch
            Reporter: Minh Do
            Priority: Minor
             Fix For: 1.2.15


When upgrading a node in 1.1.7 (or 1.1.11) cluster to 1.2.15 and inspecting the gossip information on port/Ip, I could see that the upgrading node (1.2 version) communicates to one other node in the same region using Public IP and non-encrypted port.

For the rest, the upgrading node uses the correct ports and IPs to communicate in this manner:
   Same region: private IP and non-encrypted port 
   and
   Different region: public IP and encrypted port

Because there is one node like this (or probably 2 max), we have to modify Security Group to allow the new traffics.

Without modifying the SG, the 95th and 99th latencies for both reads and writes in the cluster are very bad (due to RPC timeout).  Inspecting closer, that upgraded node (1.2 node) is contributing to all of the high latencies whenever it acts as a coordinator node. 


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)