Install DataStax Enterprise 6.8 on Debian-based systems using APT
Use these instructions for installing DataStax Enterprise (DSE) 6.8 on Debian-based systems using APT.
Some things to know about installing DataStax Enterprise
-
These instructions apply to all versions of DSE 6.8. For specific changes please see the DSE 6.8 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.8 and the DataStax Agent. It does not install OpsCenter, DataStax Studio, or DataStax Bulk Loader.
-
When connecting to DSE 6.8 from OpsCenter, use version OpsCenter 6.8; earlier versions are not supported.
|
When DSE is installed, it creates a |
Prerequisites
-
Root or sudo access.
-
Aptitude Package Management (APT) application.
-
Configure your operating system to use the latest version of Java 8:
-
Recommended. 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)
-
-
Python 3.6 through 3.11, or Python 2.7.x. Each listed version provides support for
cqlsh, but DataStax recommends using Python 3.11.Install Python 2.7 on older RHEL-based package installations
If you have an older distribution, such as CentOS 6.5, you must install Python 2.7:
-
Verify your Python version:
python -V -
If the result isn’t Python version 2.7.x, install it from the Software Collections (SCL) Repository by running the following commands:
sudo yum updatesudo yum install scl-utilssudo yum install centos-release-scl-rhsudo yum install python27sudo scl enable python27 bash -
Verify the update by checking the Python version again. Make sure the result is Python 2.7.x.
-
After logging out or restarting, you must enable python 2.7:
sudo scl enable python27 bashNote that enabling Python 2.7 in
.bash_profileor.bashrccauses the machine to hang because CentOS 6 relies on Python 2.6 for Yum.
-
Procedure
In a terminal window:
-
Verify that a required version of Java is installed:
java -versionIf OpenJDK, the results should look like:
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)If Oracle Java, the results should look like:
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)If not OpenJDK 8 or Oracle Java 8, see Install the Java Virtual Machine. DataStax recommends the latest build of a Technology Compatibility Kit (TCK) Certified OpenJDK version 8.
-
Install the libaio package. For example:
sudo apt-get install libaio1 -
Add a DataStax repository file called
/etc/apt/sources.list.d/datastax.sources.list:echo "deb https://debian.datastax.com/enterprise/ stable main" | sudo tee -a /etc/apt/sources.list.d/datastax.sources.list -
Add the DataStax repository key:
curl -L https://debian.datastax.com/debian/repo_key | sudo apt-key add - -
Update the packages:
sudo apt-get update -
Install the DSE packages:
Specify all packages; otherwise, the installation fails.
-
Install the latest version (6.8.x):
sudo apt-get install dse-full -
Install an earlier 6.8.x version:
sudo apt-get install dse=version_number-1 \ dse-full=version_number-1 \ dse-libcassandra=version_number-1 \ dse-libgraph=version_number-1 \ dse-libhadoop2-client-native=version_number-1 \ dse-libhadoop2-client=version_number-1 \ dse-liblog4j=version_number-1 \ dse-libsolr=version_number-1 \ dse-libspark=version_number-1 \ dse-libtomcat=version_number-1For example:
sudo apt-get install dse=6.8.0-1 \ dse-full=6.8.0-1 \ dse-libcassandra=6.8.0-1 \ dse-libgraph=6.8.0-1 \ dse-libhadoop2-client-native=6.8.0-1 \ dse-libhadoop2-client=6.8.0-1 \ dse-liblog4j=6.8.0-1 \ dse-libsolr=6.8.0-1 \ dse-libspark=6.8.0-1 \ dse-libtomcat=6.8.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 apt-get install dse-demos=version_number-1
-
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 below provides links to related tasks and information.
Start DSE
For single-node cluster installations only:
-
Start DSE:
sudo service dse start -
Verify that DSE is running by entering the
nodetool statuscommand:nodetool statusReview the output to verify that DSE is running:
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
cassandrauser 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.