cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-14398) Client TOPOLOGY_CHANGE messages have wrong port.
Date Thu, 19 Apr 2018 01:07:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-14398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ariel Weisberg updated CASSANDRA-14398:
---------------------------------------
    Assignee: Ariel Weisberg
    Reviewer: Greg Bestland
      Status: Patch Available  (was: Open)

https://circleci.com/gh/aweisberg/cassandra/tree/cassandra-14398-trunk
Proposed fix:
https://github.com/apache/cassandra/compare/trunk...aweisberg:cassandra-14398-trunk?expand=1

> Client TOPOLOGY_CHANGE  messages have wrong port.
> -------------------------------------------------
>
>                 Key: CASSANDRA-14398
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14398
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Greg Bestland
>            Assignee: Ariel Weisberg
>            Priority: Blocker
>             Fix For: 4.0
>
>
> Summary:
> 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-7544.  
> I was able to track it down to this specific call here.
>  [https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L1703]
> 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.
> {code:java}
> ccm create 400-1 --install-dir=/Users/gregbestland/git/cassandra
> ccm populate -n 1
> ccm start
> {code}
> 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:
> {code:java}
> ccm add node2 -i 127.0.0.2
> ccm node2 start
> {code}
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message