cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6702) Upgrading node uses the wrong port in gossiping
Date Fri, 08 May 2015 21:13:00 GMT


Ariel Weisberg commented on CASSANDRA-6702:

[~enigmacurry] I moved this one to testing just in case it's worth looking at how this might
effect other scenarios. Blake did manual testing of the fix and there are some dtests so it's
not completely untested. I am not sure how we feel about the dtest coverage and whether that
is enough.

> Upgrading node uses the wrong port in gossiping
> -----------------------------------------------
>                 Key: CASSANDRA-6702
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: 1.1.7, AWS, Ec2MultiRegionSnitch
>            Reporter: Minh Do
>            Assignee: Blake Eggleston
>            Priority: Minor
>             Fix For: 2.0.x
>         Attachments: C6702-1.2.txt, C6702-2.0.txt
> 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
>    Same region: private IP and non-encrypted port 
>    and
>    Different region: public IP and encrypted port
> Because there is one node like this (or 2 out of 12 nodes cluster in which nodes are
split equally on 2 AWS regions), 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

View raw message