[
https://issues.apache.org/jira/browse/CASSANDRA-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901129#comment-13901129
]
Jeremiah Jordan commented on CASSANDRA-6702:
--------------------------------------------
[~jasobrown] is this expected? you mention that scenario here
https://issues.apache.org/jira/browse/CASSANDRA-5669?focusedCommentId=13703209&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13703209
(publicIP on non-SSL port)
> 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.16
>
>
> 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)
