Install DataStax Enterprise 6.9 on RHEL-based systems using Yum

To install DataStax Enterprise (DSE) on SUSE, use the binary tarball installation.

Some things to know about installing DataStax Enterprise:

These instructions apply to all versions of DSE 6.9. For specific changes see the DSE 6.9 Release Notes .
When installed from a package (Yum or APT), DSE runs as a service. The service initialization script is located in /etc/init.d/dse. Run levels are not set by the package.
This procedure installs DSE 6.9 and the DataStax Agent. It does not install OpsCenter, DataStax Studio, or DataStax Bulk Loader.
When connecting to DSE 6.9 from OpsCenter, use OpsCenter version 6.8; earlier versions are not supported. See DataStax OpsCenter compatibility with DSE.

When DSE is installed, it creates a cassandra user in the database. Do not use the cassandra user in production. Failing to do so is a security risk. See Adding a Superuser Login

Prerequisites

Root or sudo access.
A supported platform.
Yum Package Management application.
Configure your operating system to use the latest version of Java 11:
- Recommended. The latest build of a TCK (Technology Compatibility Kit) Certified OpenJDK version 11.
- Supported. Oracle Java SE 11.0.x (JDK). Verify that the required Java version is used.
RedHat-compatible distributions require EPEL (Extra Packages for Enterprise Linux).
Python 3.8-3.11 required for running cqlsh.

Use OpsCenter Lifecycle Manager to automatically manage Java and JCE installs for DSE clusters. For more information about choosing a Java vendor, see Choosing a Java vendor in Lifecycle Manager.

Hardware requirements

See Recommended production settings.

Install DSE 6.9 on RHEL-based systems using Yum

End User License Agreement (EULA). By downloading this DataStax product, you agree to the terms of the EULA.

In a terminal window:

Verify that a required version of Java is installed:

java -version

DataStax recommends the latest build of a Technology Compatibility Kit (TCK) Certified OpenJDK version 11.

If OpenJDK, the results should look like:

openjdk version “11.0.x” YYYY-MM-DD
OpenJDK Runtime Environment (build 11.0.x+xx)
OpenJDK 64-Bit Server VM (build 11.0.x+xx, mixed mode)

If Oracle Java, the results should look like:

java version "11.0.x" YYYY-MM-DD LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.x+xx-LTS)
Java HotSpot(TM) 64-Bit Server VM (build 11.0.x+xx-LTS, mixed mode)

Install the libaio package. For example:
```
sudo yum install libaio
```
Add the DataStax Yum repository to a file called /etc/yum.repos.d/datastax.repo:

Set the gpgcheck=1 to perform a GPG signature check.
```
[datastax]
name={company} Repo for DSE
baseurl=https://rpm.datastax.com/enterprise/
enabled=1
gpgcheck=0
```
If you have enabled signature verification (gpgcheck=1), import the DSE repository key:
```
sudo rpm --import https://rpm.datastax.com/rpm/repo_key
```
Install the DSE packages:

Specify all packages; otherwise, the installation fails.
1. Install the latest version of DSE (6.9.x):
  sudo yum install dse-full
2. Install an earlier version of DSE 6.9.x:
  
  To view the available versions, see the Release notes.
  
  Specify all packages; otherwise, the installation fails.
  sudo yum install dse-6.9.version_number-1 \ dse-full-6.9.version_number-1 \ dse-libgraph-6.9.version_number-1 \ dse-libcassandra-6.9.version_number-1 \ dse-libhadoop2-client-6.9.version_number-1 \ dse-libsolr-6.9.version_number-1 \ dse-libtomcat-6.9.version_number-1 \ dse-liblog4j-6.9.version_number-1 \ dse-libspark-6.9.version_number-1
  For example:
  sudo yum install dse-6.9.0-1 \ dse-full-6.9.0-1 \ dse-libgraph-6.9.0-1 \ dse-libcassandra-6.9.0-1 \ dse-libhadoop2-client-6.9.0-1 \ dse-libsolr-6.9.0-1 \ dse-libtomcat-6.9.0-1 \ dse-liblog4j-6.9.0-1 \ dse-libspark-6.9.0-1
3. Optional: Install the demos:
  
  Installing the DSE demos is not recommended for production. Only install the demos in development environments to run tutorials.
  sudo yum install dse-demos-version_number-1
  Result
  
  DSE is ready for additional configuration:
  - For production, be sure to change the cassandra user. Failing to do so is a security risk. See Adding a superuser login.
  - DSE provides several types of workloads (default is transactional). See startup options for service or stand-alone installations.
  - Next Steps below provides links to related tasks and information.
Optional: Configure systemd units: RedHat systemd configuration.

Optional: Single-node cluster installations only:

Start DSE:
```
sudo service dse start
```

Verify that DSE is running:

nodetool status

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

Next Steps

You must change or delete the cassandra user created on installation. See Adding a superuser login.
Configure startup options: service or stand-alone.
If performing an upgrade, go to the next step in the Upgrade Guide.
Configuring DataStax Enterprise (DSE) - Settings for DSE Advanced Security, DSE In-Memory, DSE Advanced Replication, DSE Multi-Instance, DSE Tiered Storage, and more.
Default file locations for package installations
Default file locations for tarball installations
Changing logging locations after installation.
Starting and stopping DataStax Enterprise (DSE).
Preparing DataStax Enterprise (DSE) for production.
Recommended production settings.
Planning and testing DataStax Enterprise (DSE) cluster deployments.
Configuring the heap dump directory to avoid server crashes.
DataStax Studio documentation.
Installing DataStax Enterprise (DSE) drivers.