Start DataStax Enterprise as a standalone process

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

All nodes types are DSE nodes and run the database.

Considerations for starting a cluster

Be aware of the following when starting a DSE 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:

Analytic seed nodes.
Transactional or DSE Graph-only seed nodes.
DSE Search seed nodes.
SearchAnalytics nodes.
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

If DSE is running, stop the node.

From the directory where you installed DSE, start the node, and set the type. For example, to set a Spark node:

bin/dse cassandra -k

Node type command line options
Node/datacenter	Command
Transactional only	`bin/dse cassandra`
DSE Graph	`bin/dse cassandra -g`
DSE Analytics with Apache Spark™	`bin/dse cassandra -k`
DSE Search	`bin/dse cassandra -s`

When multiple flags are used, list them separately on the command line. For example, if the type is both Analytics and Search, make sure there is a space between -k and -s in dse cassandra -k -s.

Additional start up command examples

Here are some additional examples of start up commands for different node types:

Spark Analytics, DSE Graph, and DSE Search node:

INSTALLATION_DIRECTORY/bin/dse cassandra -k -g -s

BYOS (Bring Your Own Spark): Spark nodes run in separate Spark cluster from a vendor other than DataStax:
```
INSTALLATION_DIRECTORY/bin/dse cassandra
```

DSE Graph and BYOS:

INSTALLATION_DIRECTORY/bin/dse cassandra -g

SearchAnalytics nodes: An integrated DSE SearchAnalytics datacenter allows analytics jobs to be performed using CQL queries.
```
INSTALLATION_DIRECTORY/bin/dse cassandra -k -s
```

Check that your ring is up and running:

cd INSTALLATION_LOCATION &&
bin/nodetool status

Replace INSTALLATION_LOCATION with the path to the directory where you installed DSE.

The result of the nodetool command includes the node type, status, and state.

For a transactional node running in a normal state (UN) with virtual nodes (vnodes) enabled, the result should be similar to the following:

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 a running node in a normal state (UN) with DSE Analytics without vnodes enabled, the result should be similar to the following:

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

If DSE has problems starting, visit DataStax Support for troubleshooting articles on starting DSE.

Start DataStax Enterprise as a standalone process

Considerations for starting a cluster

Start up commands

Was this helpful?

Give Feedback