Stopping a DataStax Enterprise node

To speed up the restart process, run nodetool drain before stopping the dse service. This step writes the current memtables to disk. When you restart the node, the commit log is not read which speeds the restart process. If you have durable writes set to false, which is unlikely, there is no commit log and you must drain the node to prevent losing data.

To stop DataStax Enterprise running as a service:

nodetool drain
sudo service dse stop

To stop DataStax Enterprise running as a stand-alone process:

Running nodetool drain before using the cassandra-stop command to stop a stand-alone process is not necessary because the cassandra-stop command drains the node before stopping it.

From the installation location:

bin/dse cassandra-stop

If required, use sudo.

In the unlikely event that the cassandra-stop command fails because it cannot find the process DataStax Enterprise Java process ID (PID), the output instructs you to find the DataStax Enterprise Java process ID (PID) manually, and stop the process using its PID number.

ps auwx | grep dse

Use the PID, in the second column of the output, to stop the database.

bin/dse cassandra-stop -p PID

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,