Adding a node and then decommissioning the old node

You must prepare and start the replacement node, integrate it into the cluster, and then decommission the old node.

Procedure

Be sure to use the same version of DataStax Enterprise (DSE) on all nodes in the cluster. See Installing DataStax Enterprise 5.1.x patch releases.

  1. Prepare and start the replacement node, as described in Adding nodes to an existing cluster.

    If not using vnodes, see Adding single-token nodes to a cluster.

  2. Confirm that the replacement node is alive:

    • Run nodetool ring if not using vnodes.

    • Run nodetool status if using vnodes.

      1. Tarball and Installer No-Services path:

        <installation_location>/resources/cassandra/bin

        The status should show:

        1. nodetool ring: Up

        2. nodetool status: UN

  3. Note the Host ID of the original node; it is used in the next step.

  4. Using the Host ID of the original node, decommission the original node from the cluster using the nodetool decommission command.

  5. Run nodetool cleanup on all the other nodes in the same datacenter.

    Failure to run nodetool cleanup after adding a node may result in data inconsistencies including resurrection of previously deleted data.

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, info@datastax.com