Installing DataStax Enterprise 5.1 using the binary tarball 

Instructions for installing DataStax Enterprise 5.1 on any supported Linux-based platform.

Use these instructions for installing with root permissions on Linux-based platform using a binary tarball.

When installed from the binary tarball, DataStax Enterprise runs as a stand-alone process.

This procedure installs DataStax Enterprise 5.1 and the DataStax Agent. It does not install OpsCenter, Studio, or Graph Loader. After installing, you must configure and start DataStax Enterprise.

Note: The DataStax Installer has options to install developer related tools: Javadoc, DataStax Enterprise demos, DataStax Studio, and the DSE Graph Loader.

Prerequisites

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

Note: The latest version of DataStax Enterprise 5.1 is 5.1.5.

In a terminal window:

  1. Verify that a required version of Java is installed:
    $ java -version

    If not Oracle Java 8, or OpenJDK 8, see Installing supporting software.

    Important: Package management tools do not install Oracle Java.
  2. Download and extract the DataStax Enterprise tarball using your DataStax Academy account credentials.

    To install the latest version (5.1.5):

    $ curl --user dsa_email_address:password -L \
    https://downloads.datastax.com/enterprise/dse.tar.gz | tar xz
    To install earlier versions, add the version number in the above command. For example:
    $ curl --user daenerys@ttargaryen.com:Dothraki_warlord -L \
    https://downloads.datastax.com/enterprise/dse-5.1.0-bin.tar.gz | tar xz

    To view the available versions, see the Release notes.

    where dsa_email_address and password are your DataStax Academy account credentials.
    Attention: 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 \|.
    CAUTION:
    If you choose to run the above command, your password is retained in the shell history. To avoid this DataStax recommends using curl with the --netrc or --netrc-file option. Alternately, download the tarball from DataStax downloads.

    The files are downloaded and extracted into the dse-5.1.5 directory.

  3. To use the default data and logging directory locations, create the directories and change ownership:
    Note: If you want to define your own directory locations, see 4 and 5.
    $ sudo mkdir -p /var/lib/cassandra; sudo chown -R  $USER:$GROUP /var/lib/cassandra
    $ sudo mkdir -p /var/log/cassandra; sudo chown -R  $USER:$GROUP /var/log/cassandra
    $ sudo mkdir -p /var/lib/dsefs; sudo chown -R  $USER:$GROUP /var/lib/dsefs
    $ sudo mkdir -p /var/lib/spark; sudo chown -R  $USER:$GROUP /var/lib/spark
    $ sudo mkdir -p /var/log/spark; sudo chown -R  $USER:$GROUP /var/log/spark
    $ sudo mkdir -p /var/lib/spark/rdd; sudo chown -R  $USER:$GROUP /var/lib/spark/rdd
    $ sudo mkdir -p /var/lib/spark/worker; sudo chown -R  $USER:$GROUP /var/lib/spark/worker
    Note: If you want to define your own directory locations, see steps 4 and 5.
  4. Optional: To define your own data and logging directories:
    1. Make the directories for data and logging directories. For example:
      $ mkdir installation_location/dse-data
      $ cd dse-data
      $ mkdir commitlog
      $ mkdir saved_caches
      $ mkdir hints
    2. Go the directory containing the cassandra.yaml file:
      $ cd installation_location/resources/cassandra/conf
    3. Edit the following lines in the cassandra.yaml file:
      The location of the cassandra.yaml file depends on the type of installation:

      Package installations
      Installer-Services installations

      /etc/dse/cassandra/cassandra.yaml

      Tarball installations
      Installer-No Services installations

      installation_location/resources/cassandra/conf/cassandra.yaml
      data_file_directories: installation_location/dse-data
      commitlog_directory: installation_location/dse-data/commitlog
      saved_caches_directory: installation_location/dse-data/saved_caches
      hints_directory: installation_location/dse-data/hints
  5. Optional: To define your own Spark directories:
    1. Make the directories for the Spark lib and log directories.
    2. Edit the spark-env.sh file to match the locations of your Spark lib and log directories, as described in Configuring Spark nodes.
      The default location of the spark-env.sh file depends on the type of installation:

      Package installations
      Installer-Services installations

      /etc/dse/spark/spark-env.sh

      Tarball installations
      Installer-No Services installations

      installation_location/resources/spark/conf/spark-env.sh
    3. Make a directory for the DSEFS data directory and set its location in dsefs_options.

    DataStax Enterprise is ready for additional configuration.

  6. Optional: Single-node cluster installations only:
    1. Start DataStax Enterprise from the installation directory:
      $ bin/dse cassandra
      where the installation directory is either:
      • /usr/share/dse
      • the directory where you installed DataStax Enterprise.
      Note: For other start options, see Starting DataStax Enterprise as a stand-alone process.
    2. Verify that DataStax Enterprise is running from the installation directory:
      $ bin/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

The location of the cassandra.yaml file depends on the type of installation:

Package installations
Installer-Services installations

/etc/dse/cassandra/cassandra.yaml

Tarball installations
Installer-No Services installations

installation_location/resources/cassandra/conf/cassandra.yaml
The location of the dse.yaml file depends on the type of installation:

Package installations
Installer-Services installations

/etc/dse/dse.yaml

Tarball installations
Installer-No Services installations

installation_location/resources/dse/conf/dse.yaml