Stopping a DataStax Enterprise node
Stopping DataStax Enterprise on a node.
To speed up the restart process, before stopping the dse service, run nodetool drain. 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 (DSE) running as a stand-alone process:
Note: 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 ## Use sudo if needed
In the unlikely event that the cassandra-stop command fails because it cannot find
the DSE Java process ID
(PID), the output instructs you to find the DSE Java process ID (PID) manually, and stop the
process using its PID
number.
ps auwx | grep dse
bin/dse cassandra-stop -p PID ## Use sudo if needed
Note: If you have trouble, see Troubleshooting DataStax Enterprise.