Starting DataStax Enterprise as a stand-alone process

Steps for starting the DataStax Enterprise process when DataStax Enterprise was installed from a tarball.

Steps for starting the DataStax Enterprise (DSE) process when DataStax Enterprise was installed from a tarball.

All nodes types are DataStax Enterprise nodes and run the database.

Considerations for starting a cluster

Be aware of the following when starting a DataStax Enterprise cluster:

Nodes must be segregated by datacenters
Transactional, DSE Search, DSE Analytics, and SearchAnalytics 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 datacenters.

DSE Graph can be enabled on any node in any 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, DSE Search, and SearchAnalytics nodes. Deploy in this order:
  1. Analytic seed nodes.
  2. Transactional or DSE Graph-only seed nodes.
  3. DSE Search seed nodes.
  4. SearchAnalytics nodes.
  5. Remaining nodes one at a time. See Initializing multiple datacenters per workload type.
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

  1. Start the node from the installation_location.
  2. Set the type.
    Node/datacenter Command
    Transactional only bin/dse cassandra
    DSE Graph bin/dse cassandra -g
    DSE Analytics with Spark bin/dse cassandra -k
    DSE Search bin/dse cassandra -s
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.
Table 1. Starting examples
Node type Settings
From the installation_location:
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
SearchAnalytics nodes

An integrated DSE SearchAnalytics datacenter allows analytics jobs to be performed using CQL queries.

bin/dse cassandra -k -s

Prerequisites

Be sure to read the Considerations for starting a cluster.

You can also use OpsCenter to start and stop nodes.

Procedure

  1. If DataStax Enterprise is running, stop the node.
  2. From the install directory, start the node. For example, to set a Spark node:
    bin/dse cassandra -k
  3. To check that your ring is up and running:
    cd installation_location && 
    bin/nodetool status
    where the installation directory is either:
    • /usr/share/dse
    • DataStax Enterprise installation directory
    Note: If DSE has problems starting, see Troubleshooting starting and installing DSE.

    The nodetool command shows the node type and the status. For a transactional node running in a normal state (UN) with virtual nodes (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