Replacing a running node

You can replace a node that is currently running and avoid streaming the data twice or running cleanup using these steps.

If you’ve written data using a consistency level of ONE, you risk losing data because the node might contain the only copy of a record. Be absolutely sure that no application uses consistency level ONE.


  1. Stop DataStax Enterprise on the node to be replaced.

  2. Follow the instructions for replacing a dead node using the old node’s IP address for -Dcassandra.replace_address.

  3. Ensure that consistency level ONE is not used on this node.

Related information

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,