cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Bestland (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-14398) Client TOPOLOGY_CHANGE messages have wrong port.
Date Wed, 18 Apr 2018 22:01:00 GMT
Greg Bestland created CASSANDRA-14398:

             Summary: Client TOPOLOGY_CHANGE  messages have wrong port.
                 Key: CASSANDRA-14398
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Greg Bestland
             Fix For: 4.0.x


TOPOLOGY_CHANGE events that are recieved by the client(Driver), with C* 4.0 (Trunk). Contain
the storage port (7000) rather than the native port (9042). I believe this is due to changes
stuck in for CASSANDRA-17544.  

I was able to track it down to this specific call here.


We need an accurate port number from this Topology change event, otherwise we won't be able
to correlate node up event against the system.peers_v2 table accurately.

C* version I'm testing against : 4.0.x (trunk)

Steps to reproduce:

1. create a single node, cluster, in this case I'm using ccm.
ccm create 400-1 --install-dir=/Users/gregbestland/git/cassandra
ccm populate -n 1
ccm start
2. Connect the java driver, and check metadata.
 see that there is one node with the correct native port (9042).

3. Add a brand new node:
ccm add node2 -i
ccm node2 start
4. Incoming topology change message to client will have the storage port, rather then the
native port in the message.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message