Install DataStax Enterprise 6.8 using the binary tarball
These instructions apply to all versions of DSE 6.8. Review specific changes in the DSE 6.8 Release notes.
A DSE binary tarball enables:
-
DSE to run as a standalone process.
-
A user to install DSE with or without root permissions.
A deployment of DSE creates a |
Default configuration files location
The default location of the spark-env.sh
file depends on the type of installation:
Package installations |
|
Tarball installations |
|
The location of the cassandra.yaml
file depends on the type of installation:
Package installations |
|
Tarball installations |
|
Prerequisites
The following requirements must be met before you install DSE 6.8 using the binary tarball:
-
Configure your operating system to use the latest version of Java 8:
-
You must set the
$JAVA_HOME
environment variable to point to Java 11 when running multiple Java runtime environments. -
Recommended: Access the latest build of a TCK (Technology Compatibility Kit) Certified OpenJDK version 8. For example, OpenJDK 8 (1.8.0_242 minimum). DataStax’s recommendation changed due to the end of public updates for Oracle JRE/JDK 8. See Oracle Java SE Support Roadmap.
-
Supported: Oracle Java SE 8 (JRE or JDK) (1.8.0_151 minimum)
-
-
RedHat-compatible distributions require EPEL (Extra Packages for Enterprise Linux).
-
Python 2.7.x or 3.6+. Both are supported for
cqlsh
. For older RHEL distributions, see Installing Python 2.7 on older RHEL-based package installations.
Download and deploy DataStax Enterprise (DSE) 6.8
End User License Agreement (EULA). By downloading this DataStax product, you agree to the terms of the EULA. |
-
Verify that you have installed a supported version of Java:
-
Terminal window command
-
OpenJDK sample result
-
Oracle Java sample result
java -version
openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b09) OpenJDK 64-Bit Server VM (build 25.242-b09, mixed mode)
java version "1.8.0_241" Java(TM) SE Runtime Environment (build 1.8.0_241-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.241-b13, mixed mode)
DataStax recommends the latest build of a Technology Compatibility Kit (TCK) Certified OpenJDK version 8.
If the output shows that OpenJDK 8 or Oracle Java 8 is not installed, see Installing the JDK.
-
-
From a terminal window, install the
libaio
package that matches your environment:-
RHEL platform
-
Debian platform
sudo yum install libaio
sudo apt-get install libaio1
-
-
Download and extract the binary tarball files manually or use
curl
:-
Manual download and extract
-
curl
download and extract
-
Extract the binary tarball files into the directory of your choice:
tar -xzvf dse-6.8.x-bin.tar.gz
During the manual method, the shell history retains your password. To avoid this security issue, use
curl
with its --netrc or --netrc-file option.
Latest version:
curl -L https://downloads.datastax.com/enterprise/dse.tar.gz | tar xz
Earlier versions:
curl -L https://downloads.datastax.com/enterprise/dse-version_number-bin.tar.gz | tar xz
The command downloads and extracts the files into the 6.8 directory. Start DSE from this installation directory and store logs and data there, or define your own locations.
-
-
Use either the default data and logging directory locations, or define your own directory locations:
-
Default directory locations
-
Define your own directory locations
To use the default data and logging directory locations, create and change ownership for the following:
-
/var/lib/cassandra
-
/var/log/cassandra
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
-
In the installation location, make the directories for data and logging directories. For example:
mkdir dse-data && cd dse-data && mkdir data && mkdir commitlog && mkdir saved_caches && mkdir hints && mkdir cdc_raw
-
Change to the directory that contains the
cassandra.yaml
file:cd installation_location/resources/cassandra/conf
-
Update the following lines in the
cassandra.yaml
file to match the custom locations:data_file_directories: - full_path_to_installation_location/dse-data/data commitlog_directory: full_path_to_installation_location/dse-data/commitlog saved_caches_directory: full_path_to_installation_location/dse-data/saved_caches hints_directory: full_path_to_installation_location/dse-data/hints cdc_raw_directory: full_path_to_installation_location/cdc_raw
-
-
To store logs and data in the installation location, use the environment variable
CASSANDRA_LOG_DIR
to specify the location of the logs directory:cd dse-6.8.x CASSANDRA_LOG_DIR=`<pwd>`/logs bin/dse cassandra
-
Apply additional configurations to your DSE installation:
-
For production, be sure to change the default
cassandra
user; otherwise, it is a security risk. See Create a new superuser account for your database. -
DataStax Enterprise (DSE) provides several types of workloads; the default is transactional. See startup options for service or standalone installations.
-
Next Steps provides links to related tasks and information.
-
-
Optional: To use DSE analytics, choose either the default Apache Spark™ data and logging directory locations or define your locations:
-
Default directory locations
-
Define your own Spark directory locations
To use the default Spark directory locations, create and change ownership for the following:
-
/var/lib/dsefs
-
/var/lib/spark
-
/var/log/spark
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/log/spark/master; sudo chown -R $USER:$GROUP /var/log/spark/master && sudo mkdir -p /var/log/spark/alwayson_sql; sudo chown -R $USER:$GROUP /var/log/spark/alwayson_sql && sudo mkdir -p /var/lib/spark/worker; sudo chown -R $USER:$GROUP /var/lib/spark/worker
-
In the installation_location directory where you extracted DSE, make the directories for data and logging directories. For example:
mkdir dsefs && mkdir spark && cd spark && mkdir log && mkdir rdd && mkdir worker && cd log && mkdir worker && mkdir master && mkdir alwayson_sql
-
Change to the directory that contains the
spark-env.sh
file:cd installation_location/resources/spark/conf
-
Uncomment and update the following lines in the
spark-env.sh
file:export SPARK_WORKER_DIR="full_path_to_installation_location/spark/worker" export SPARK_EXECUTOR_DIRS="full_path_to_installation_location/spark/rdd" export SPARK_WORKER_LOG_DIR="full_path_to_installation_location/spark/log/worker" export SPARK_MASTER_LOG_DIR="full_path_to_installation_location/spark/log/master" export ALWAYSON_SQL_LOG_DIR="full_path_to_installation_location/spark/log/alwayson_sql"
-
Change to the directory that contains the dsefs_options file:
cd installation_location/resources/dse/conf
-
Uncomment and update the DSEFS directory in
dse.yaml
:work_dir: full_path_to_installation_location/dsefs
DSE 6.8 is ready for additional configuration. See Next Steps.
-
-
Single-node cluster installations only:
-
Start DSE from its installation directory, where the installation directory is the directory where you installed DSE.
bin/dse cassandra
For other standalone start options, see Starting DataStax Enterprise as a standalone process.
-
Verify that DSE is running from the installation directory:
-
Nodetool command
-
Results using vnodes
-
Results not using vnodes
bin/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
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
-
-
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.
-
Changing logging locations after installation.
-
Planning and testing DataStax Enterprise (DSE) cluster deployments.
-
Configuring the heap dump directory to avoid server crashes.