Installing DataStax Enterprise 6.0 on RHEL-based systems using Yum

Instructions for installing DataStax Enterprise 6.0 using Yum repositories on RHEL-based systems. Root permissions are required.

Instructions for installing DataStax Enterprise (DSE) 6.0 on RHEL-based systems using Yum.

To install on SUSE, use the binary tarball installation.

Some things to know about installing DSE

  • The latest version of DataStax Enterprise 6.0 is 6.0.6.
  • When installed from a package (Yum or APT), DataStax Enterprise 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.0 and the DataStax Agent. It does not install OpsCenter, DataStax Studio, Graph Loader, or DataStax Bulk Loader.
  • When connecting to DSE 6.0 from OpsCenter, use version OpsCenter 6.5; earlier versions are not supported. See DataStax OpsCenter compatibility with DSE.
Warning: 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

Note: For more information about managing Java, see Managing Java installs.
Table 1. Hardware requirements
Requirement Minimum Production
CPUs 2 16
Memory 8 GB 24 GB
Data directory 20 GB 200 GB
Commit log directory 20 GB 200 GB
Saved caches directory 20 GB 200 GB
Logs directory 20 GB 200 GB
Also see Recommended production settings and the DataStax Enterprise Reference Architecture white paper.

Procedure

In a terminal window:

  1. Verify that a required version of Java is installed: 
    java -version
    If OpenJDK, the results should look like:
    openjdk version "1.8.0_171"
OpenJDK Runtime Environment (build 1.8.0_171-8u171-b11-0ubuntu0.16.04.1-b11)
OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)
    If Oracle Java, the results should look like:
    java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)

    If not OpenJDK 8 or Oracle Java 8, see Installing supporting software on DataStax Enterprise 6.0.

  2. Install the libaio package. For example: 
    sudo yum install libaio
  3. Add the DataStax Yum repository to a file called /etc/yum.repos.d/datastax.repo:
    Note: Set the gpgcheck=1 to perform a GPG signature check.
    [datastax] 
name = DataStax Repo for DataStax Enterprise
baseurl=https://DSA_email_address:downloads_key@rpm.datastax.com/enterprise/
enabled=1
gpgcheck=0

    where DSA_email_address and downloads_key are your DataStax Academy email address and My Downloads Key. Depending on your environment, you might need to replace @ in your email address with %40 and escape any character in your password that is used in your operating system's command line. Examples: \! and \|.

    For backward compatibility, you can use your DataStax Academy Profile Name and password instead of your email address and Downloads Key.

  4. If you have enabled signature verification (gpgcheck=1), import the DataStax Enterprise repository key: 
    sudo rpm --import https://rpm.datastax.com/rpm/repo_key
  5. Install the DataStax Enterprise package:
    • Install the latest version (6.0.6):
      sudo yum install dse-full-6.0.6-1
    • Install an earlier 6.0.x version:
      Note: To view the available 6.0.x versions, see the Release notes.
      sudo yum install dse-full-version_number-1
      For example:
      sudo yum install dse-full-6.0.0-1
    • Optional: Install the demos:
      Attention: Installing the DSE demos is not recommended for production. Only install the demos in development environments to run tutorials.
      sudo yum install dse-demos-6.0.6-1
    DataStax Enterprise is ready for additional configuration. See What's next.
  6. Optional: Single-node cluster installations only:
    1. Start DataStax Enterprise: 
      sudo service dse start

      For more start options, see Starting DataStax Enterprise as a service.

    2. Verify that DataStax Enterprise is running: 
      nodetool status
      Results using vnodes:
      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
      Results not using vnodes:
      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

What's next