Installing DataStax Enterprise 5.1 on Debian-based systems using APT
Learn how to install DataStax Enterprise 5.1 on Debian-based systems using APT.
Some things to know about installing DSE
-
When installed with 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 DataStax Enterprise 5.1 and the DataStax Agent. It does not install OpsCenter, Studio, or Graph Loader.
-
If using OpCenter 6.0, override the default DataStax Agent. However, OpsCenter 6.8 is recommended. See DSE product compatibility. After installation:
sudo apt-get install datastax-agent-6.0.supported_version-1To install the agent during installation, add
datastax-agent-6.0.supported_version-1to the installation command in 5.
|
SECURITY RISK When DSE is installed, it creates a superuser called |
|
For more information about managing Java, see Managing Java installs. |
Prerequisites
-
An IBMid.
-
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.
-
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_151 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 DSE on Debian-based systems using APT
-
Verify that a required version of Java is installed:
java -versionDataStax recommends the latest build of a Technology Compatibility Kit (TCK) Certified OpenJDK version 8.
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 Install the Java Virtual Machine.
-
Download the DSE DEB package 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 Select from IBM DataStax Enterprise list.
-
Select All in the Platform 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.
-
Review the terms and conditions, and then click I agree.
-
-
Click the DSE DEB package link to download the file, for example,
dse-5.1.48-deb.zip. -
Extract the DEB files from the
.zipfile:sudo unzip dse-5.1.48-deb.zipYou can use the package signing public key (
dse-deb-signing.pub.key) in the file to set up and verify the DEB packages. -
Set up a local APT repository to host the downloaded DSE Debian package.
For more information, see Setting up a Debian repository.
-
Add a DataStax repository file called
/etc/apt/sources.list.d/datastax.sources.list:echo "deb [trusted=yes] file:**REPOSITORY_DIRECTORY** ./" | sudo tee -a /etc/apt/sources.list.d/datastax.sources.listReplace
REPOSITORY_DIRECTORYwith the path to the repository directory.The
[trusted=yes]option allows APT to use the repository without GPG key verification. -
Update the packages:
sudo apt-get update -
Install the DSE packages:
Specify all packages; otherwise, the installation fails.
-
Install the latest version of DSE (5.1.x):
sudo apt-get install dse-full -
Install an earlier version of DSE 5.1.x:
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:
Specify all packages; otherwise, the installation fails.
sudo apt-get install dse=5.1.48-1 \ dse-full=5.1.48-1 \ dse-libcassandra=5.1.48-1 \ dse-libgraph=5.1.48-1 \ dse-libhadoop2-client-native=5.1.48-1 \ dse-libhadoop2-client=5.1.48-1 \ dse-liblog4j=5.1.48-1 \ dse-libsolr=5.1.48-1 \ dse-libspark=5.1.48-1 \ dse-libtomcat=5.1.48-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-1Result
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.
-
-
-
Single-node cluster installations only:
-
Start DSE:
sudo service dse start -
Verify that DSE is running:
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 Creating superuser accounts. -
Configuring DataStax Enterprise- Settings for DSE Advanced Security, In-Memory, DSE Advanced Replication, DSE Multi-Instance, DSE Tiered Storage, and more.
-
Configuration and log file locations - Services and package installations.
-
Configuration and log file locations - No Services and tarball installations.
-
Changing logging locations after installation.