[jira] [Assigned] (CASSANDRA-7122) Replacement nodes have null entries in system.peers

["Brandon Williams (JIRA)" <ji...@apache.org>]

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

Brandon Williams reassigned CASSANDRA-7122:
-------------------------------------------

    Assignee: Brandon Williams

> Replacement nodes have null entries in system.peers
> ---------------------------------------------------
>
>                 Key: CASSANDRA-7122
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7122
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Richard Low
>            Assignee: Brandon Williams
>         Attachments: 7122.txt
>
>
> If a node is replaced with -Dcassandra.replace_address, the new node has mostly null entries in system.peers:
> {code}
> > select * from system.peers;
>  peer      | data_center | host_id | rack | release_version | rpc_address | schema_version | tokens
> -----------+-------------+---------+------+-----------------+-------------+----------------+--------------------------
>  127.0.0.3 |        null |    null | null |            null |        null |           null | {'-3074457345618258602'}
> {code}
> To reproduce, simply kill a node and replace it. The entries are correctly populated if the replacement node is restarted but they are never populated if it isn't.
> I can think of at least two bad consequences of this:
> 1. Drivers like Datastax java-driver use the peers table to find the rpc_address and location info of a node. If the entires are null it assumes rpc_address=ip and the node is in the local DC.
> 2. When using GossipingPropertyFileSnitch and node won't persist the DC/rack of another node so may not be able to locate it during restarts.
> I reproduced in 1.2.15 but from inspection it looks to be present in 1.2.16 and 2.0.7.



--
This message was sent by Atlassian JIRA
(v6.2#6252)