Starting DataStax Enterprise as a stand-alone process

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

Steps for starting the DataStax Enterprise process when DataStax Enterprise was installed from a tarball or from the DataStax Installer with the No Services option.
Note: All nodes types are DataStax Enterprise nodes and run the Cassandra database.

Considerations 

Be aware of the following when starting a cluster:

Nodes must be segregated by datacenters 
With the exception of SearchAnalytics nodes, transactional (Cassandra), DSE Search, and DSE Analytics nodes must be in separate datacenters. For example, in a cluster with both DSE Search and transactional nodes, all DSE Search nodes must be in a one or more search datacenters and all transactional nodes must be in one or more Cassandra datacenters.
Note: DSE Graph can be enabled on any node in any datacenter. It no longer needs to be enabled on every node within a datacenter.
Deploying a mixed-workload cluster 
When deploying one or more datacenters for each type of node, first determine which nodes to start as transactional, analytic, DSE Graph only, DSE Graph plus other types, and DSE Search nodes. Deploy in this order:
  1. Analytic seed nodes.
  2. Cassandra or DSE Graph only seed nodes.
  3. DSE Search seed nodes.
  4. Remaining nodes one at a time. See Multiple datacenter deployment.
Attention: When using DSE Hadoop, do not start all the nodes at the same time, as this causes contention among Hadoop nodes to become the Job Tracker.
DSE Analytics nodes 
Before starting DSE Analytics nodes, ensure that the replication factor is configured correctly for the analytics keyspaces. Every time you add a new datacenter, you must manually increase the replication factor of the dse_leases keyspace for the new DSE Analytics datacenter.

Start up commands

Set the type of node:
Node/datacenter Command
Cassandra only $ bin/dse cassandra
DSE Graph $ bin/dse cassandra -g
Note: DSE Graph does not support Hadoop.
DSE Analytics with Spark $ bin/dse cassandra -k
DSE Search $ bin/dse cassandra -s
DSE Hadoop $ bin/dse cassandra -t

DSE Hadoop uses Hadoop 1.0.4 libraries uses built-in Hadoop Job Trackers and Task Trackers.

Note: When multiple flags are used, list them separately on the command line. For example, ensure there is a space between -k and -s in dse cassandra -k -s.
Examples
Node type Settings
Spark Analytics, DSE Graph, and DSE Search node $ bin/dse cassandra -k -g -s
BYOS (Bring Your Own Spark)

Spark nodes run in separate Spark cluster from a vendor other than DataStax.

$ bin/dse cassandra
DSE Graph and BYOS $ bin/dse cassandra -g
DSE Graph and BYOH (DSE Graph with Bring Your Own Hadoop)

Hadoop nodes run in separate Hadoop cluster from a vendor other than DataStax.

$ bin/dse cassandra -g
SearchAnalytics nodes

An integrated DSE SearchAnalytics cluster allows analytics jobs to be performed using search queries.

$ bin/dse cassandra -k -s
DSE Graph and DSE Hadoop Not supported.

Prerequisites

Be sure to read the Considerations.

Procedure

If DataStax Enterprise is running, stop the node.

Note: You can also use OpsCenter to start and stop nodes.

  1. From the install directory, start the node. For example, to set a Spark node:
    $ bin/dse cassandra -k
  2. To check that your ring is up and running:
    $ cd install_location
    $ bin/nodetool status
    All nodes are DataStax Enterprise nodes and run the Apache Cassandra™ database.
    Note: If you have trouble, see Troubleshooting starting DataStax Enterprise.

    The nodetool command shows the node type and the status. For a Cassandra node running in a normal state (UN) with vnodes enabled shows:

    Datacenter: Cassandra
    =====================
    Status=Up/Down
    |/ State=Normal/Leaving/Joining/Moving
    --  Address    Load       Tokens  Owns    Host ID                               Rack
    UN  127.0.0.1  82.43 KB   128     ?       40725dc8-7843-43ae-9c98-7c532b1f517e  rack1

    For example, a running node in a normal state (UN) with DSE Analytics without vnodes enabled shows:

    Datacenter: Analytics
    =====================
    Status=Up/Down
    |/ State=Normal/Leaving/Joining/Moving
    --  Address         Load       Owns    Host ID                               Token                 Rack
    UN  172.16.222.136  103.24 KB  ?       3c1d0657-0990-4f78-a3c0-3e0c37fc3a06  1647352612226902707   rack1