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 DSE OpsCenter, DataStax Studio, or DataStax Bulk Loader (DSBulk).
-
When connecting to DSE 6.9 from DSE OpsCenter, use DSE OpsCenter version 6.8; earlier versions are not supported.
|
When DSE is installed, it creates a |
Prerequisites
-
An IBMid with MFA enabled.
-
If you are an existing IBM customer with an IBMid, you can continue to use your established account.
-
If you don’t have an IBMid, you can create one.
-
If your company uses Enterprise Federation (EF) for authentication with corporate credentials, see the EF documentation.
-
-
Root or sudo access.
-
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 DSE OpsCenter Lifecycle Manager (LCM) to automatically manage Java and JCE installs for DSE clusters. For more information about choosing a Java vendor, see Choosing a Java vendor in LCM. |
Install DSE 6.9 on RHEL-based systems using Yum
-
Verify that a required version of Java is installed:
java -versionIf 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)DataStax recommends the latest build of a Technology Compatibility Kit (TCK) Certified OpenJDK version 11.
-
Install the
libaiopackage. For example:sudo yum install libaio -
Download the DSE RPM packages from Fix Central:
-
Sign in to Fix Central.
-
In the Product selector field, enter
IBM DataStax Enterprise. -
Select the DataStax Enterprise version you want to install from the Release list, and then click Continue.
-
On the Identify fixes page, click Continue to use the default Browse for fixes option.
-
Select the fix pack (DataStax Enterprise version) you want to install, and then click Continue.
-
On the Download options page, select the Download using your browser (HTTPS), and then click Continue.
This step is only required the first time you download a file using Fix Central. If you need to change your download method for subsequent downloads, use the Change download options link in the Download options section of Fix Central pages.
-
Review the terms and conditions, and then click I agree.
-
-
Click the DSE RPM package link to download the file, for example,
dse-6.9.15-rpm.zip. -
Extract the RPM files from the
.zipfile:sudo unzip dse-6.9.15-rpm.zipYou can use the package signing public key (
dse-rpm-signing.pub.key) in the file to set up and verify the RPM packages. -
Import the package signing public key:
sudo rpm --import dse-rpm-signing.pub.key -
Set up a local Yum repository to host the downloaded RPM files:
- Apache
-
See Apache in the Red Hat documentation for more information.
- nginx
-
See nginx in the Red Hat documentation for more information.
- Red Hat Satellite
-
See Uploading content to custom RPM repositories in the Red Hat Satellite documentation for more information.
-
Add the local DataStax Yum repository to a file called
/etc/yum.repos.d/datastax.repo:[datastax] name={company} Repo for DSE baseurl=file://**REPOSITORY_DIRECTORY_PATH** enabled=1 gpgcheck=0 -
Install the DSE packages:
Specify all packages; otherwise, the installation fails.
-
Install the latest version of DSE (6.9.x):
sudo yum install dse-full -
Install an earlier version of DSE 6.9.x:
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-1For 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 -
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
-
-
Optional: Configure systemd units in RedHat systemd configuration.
DSE is ready for additional configuration:
-
For production, be sure to change the
cassandrauser. 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 provides links to related tasks and information.
Start DSE
On Single-node cluster installations only:
-
Start DSE:
sudo service dse start -
Verify that DSE is running:
nodetool statusResultDatacenter: 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
-
If performing an upgrade, go to the next step in the Upgrade Guide.
-
Configure DataStax Enterprise settings for DSE Advanced Security, DSE In-Memory, DSE Advanced Replication, DSE Multi-Instance, DSE Tiered Storage, and more.
-
Review the default file locations for package installations.
-
Change the logging locations after installation.
-
Configure the heap dump directory to avoid server crashes.