Starting DataStax Enterprise as a stand-alone process 

Starting the DataStax Enterprise process when DataStax Enterprise was installed from the DataStax Installer with the No Services option or from a tarball.

If running a mixed-workload cluster (one or more datacenters for each type of node), determine which nodes to start as analytics, Cassandra, and DSE Search nodes. Begin with the seed nodes first — analytics seed node, followed by the Cassandra seed node — then start the remaining nodes in the cluster one at a time. For more information, see Multiple datacenter deployment.

Attention: Do not start all the nodes at the same time, because this causes contention among nodes to become the Job Tracker.


  1. From the install directory:
    Option Description
    Cassandra node $ bin/dse cassandra
    BYOH node $ bin/dse cassandra
    DSE Hadoop node $ bin/dse cassandra -t
    DSE Search node $ bin/dse cassandra -s
    Spark only node $ bin/dse cassandra -k ## Starts Spark trackers on a cluster of analytics nodes
    Spark + DSE Hadoop $ bin/dse cassandra -k -t ## Starts a node in Spark and in Hadoop mode
    SearchAnalytics node $ bin/dse cassandra -s -k ## Starts a node in SearchAnalytics mode
    Attention: All nodes are DataStax Enterprise nodes and run the Cassandra database.
  2. Start the DataStax agent:
    $ ./datastax-agent/bin/datastax-agent
  3. To check that your ring is up and running:
    $ cd install_location
    $ bin/nodetool status
    If you are running an analytics node, there are several methods for designating the Job Tracker node.