[ https://issues.apache.org/jira/browse/CASSANDRA-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990938#comment-13990938 ]
Brandon Williams commented on CASSANDRA-7122: --------------------------------------------- When I replace with a different ip, I get the inverse problem: {noformat} peer | data_center | host_id | rack | release_version | rpc_address | schema_version | tokens ---------------+-------------+--------------------------------------+-------+-----------------+---------------+--------------------------------------+-------------------------- 10.208.35.225 | datacenter1 | 36f346bc-d186-415e-a1aa-8d4839823755 | rack1 | 1.2.16-SNAPSHOT | 10.208.35.225 | 7ed7c061-913f-3cf0-9c8d-a192d3a988db | null {noformat} Tokens is null, but that is the IP that was replaced and shouldn't be there at all. This patch fixes this behavior too, however. > 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 > Fix For: 1.2.17 > > 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)