[
https://issues.apache.org/jira/browse/CASSANDRA-8382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298993#comment-14298993
]
Anuj commented on CASSANDRA-8382:
---------------------------------
Just bouncing C* didnt remove old IPs. We finally cleared gossip state on all
nodes by adding following line at end of cassandra-env.sh:
JVM_OPTS="$JVM_OPTS -Dcassandra.load_ring_state=false"
This solved our issue. I hope the procedure is correct and we need not clear
gossip info by other methods e.g. sudo rm -r
/var/lib/cassandra/data/system/peers/* or executing
Gossiper.unsafeAssassinateEndpoints(ip_address) via JConsole as mentioned at
http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_gossip_purge.html
> Procedure to Change IP Address without Data streaming is Missing in Cassandra
> Documentation
> -------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-8382
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8382
> Project: Cassandra
> Issue Type: Bug
> Components: Documentation & website
> Environment: Red Hat Linux , Cassandra 2.0.3
> Reporter: Anuj
>
> Use Case:
> We have a Geo-Red setup with 2 DCs (DC1 and DC2) having 3 nodes each. Listen
> address and seeds of all nodes are Public IPs while rpc addresses are private
> IPs. Now, we want to decommission a DC2 and change public IPs in listen
> address/seeds of DC1 nodes to private IPs as it will be a single DC setup.
> Issue:
> Cassandra doesn’t provide any standard procedure for changing IP address of
> nodes in a cluster. We can bring down nodes, one by one, change their IP
> address and perform the procedure mentioned in “ Replacing a Dead Node” at
> http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_replace_node_t.html
> by mentioning public IP of the node in replace_address option. But
> procedure recommends that you must set the auto_bootstrap option to true. We
> don’t want any bootstrap and data streaming to happen as data is already
> there on nodes. So, our questions is : What’s the standard procedure for
> changing IP address of Cassandra nodes while making sure that no data
> streaming occurs and gossip state is not corrupted.
> We are using vnodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
