So if the idea is to completely remove it, just deleting the corresponding
entry from system.peers should do it.
Some versions of Cassandra have a bug that leaves the entry in the
system.peers table after decommissioning, and the fix is just to delete it.
Here is the link to the JIRA:
https://iss
the below solution should work.
For each node in the cluster :
a : Stop cassandra service on the node.
b : manually delete data under $data_directory/system/peers/ directory.
c : In cassandra-env.sh file, add the line JVM_OPTS="$JVM_OPTS
-Dcassandra.load_ring_state=false".
d : Restart service
On 10/08/2015 10:27 AM, Robert Wille wrote:
nodetool status doesn’t list it, but its still in system.peers, and
OpsCenter still shows it. When I run nodetool removenode, it says
that it can’t find the node.
How do I completely get rid of it?
https://twitter.com/faltering/status/559845791741657
We had some problems with a node, so we decided to rebootstrap it. My IT guy
screwed up, and when he added -Dcassandra.replace_address to cassandra-env.sh,
he forgot the closing quote. The node bootstrapped, and then refused to join
the cluster. We shut it down, and then noticed that nodetool st
