Install DataStax Enterprise (DSE) 5.1 on RHEL-based systems with Yum
Use these instructions to install DataStax Enterprise (DSE) 5.1 on RHEL-based systems using Yum. Optionally, this process can install the DataStax Agent for use with DSE OpsCenter. It doesn’t install DSE OpsCenter, DataStax Studio, or Graph Loader.
For new deployments, DataStax recommends the latest patch release. If you are scaling an existing deployment, install the same patch release as the existing nodes. For a summary of features and changes in each release, see the DSE 5.1 release notes.
When installed from a package, DSE runs as a service.
The service initialization script is located in /etc/init.d/dse.
Run levels aren’t set by the package.
|
When you install DSE, it automatically creates a |
To install DataStax Enterprise (DSE) on SUSE, use the binary tarball installation. For other installation options, see Which install method should I use?.
Prerequisites
-
Prepare an environment where you want to install DSE, including sufficient hardware, a supported platform, and root or sudo access.
-
Install Yum package manager.
-
For RHEL-compatible platforms, enable Extra Packages for Enterprise Linux (EPEL).
-
Install a supported Java runtime: OpenJDK 8 (recommended) or Oracle Java SE 8 (JDK).
If you install multiple Java versions, set your
$JAVA_HOMEenvironment variable to Java 8. -
To run the CQL shell (
cqlsh), install a supported Python version.To verify your Python version, run
python -V.If you require Python 2.7, install it from the Software Collections (SCL) Repository:
-
Run the following commands:
sudo yum updatesudo yum install scl-utilssudo yum install centos-release-scl-rhsudo yum install python27sudo scl enable python27 bash -
Check your Python version again to confirm that it is 2.7.
-
Restart the system or log out and log back in, and then enable python 2.7:
sudo scl enable python27 bashEnabling Python 2.7 in
.bash_profileor.bashrccauses the machine to hang because CentOS 6 relies on Python 2.6 for Yum.
-
-
For production installations and simulated production test environments, review the recommended settings.
Some settings can be applied before installing DSE. For settings that require a running DSE instance, plan to apply them after the installation.
-
If you plan to use DSE OpsCenter:
-
DSE OpsCenter 6.8 is recommended for DSE 5.1.
-
If using DSE OpsCenter 6.0, override the default DataStax Agent version that is installed with this process by adding
datastax-agent-6.0.supported_version-1to your installation command. Alternatively, you can install the DataStax Agent separately or after installation with the following command:sudo yum install datastax-agent-6.0.supported_version-1 -
To use DSE OpsCenter Lifecycle Manager (LCM) to automatically manage the Java runtime for DSE clusters, see Manage Java installs and Choose a Java vendor in LCM.
-
Install DSE
-
Find DSE 5.1 on IBM Fix Central:
-
Go to Fix Central.
-
In the Product selector field, begin typing
IBM DataStax Enterprise, and then select that option from the menu. -
In the Release field, select the version that you want to install.
-
Click Continue.
-
On the Identify fixes page, click Continue to use the default Browse for fixes option.
-
On the Select fixes page, select the fix pack (DSE version) you want to install, and then click Continue.
Depending on the product and version, more fix packs might be available if you set the Platform filter to All, and then click Submit.
-
If prompted, sign in with your IBMid.
An IBMid account with MFA enabled is required. If you don’t have one, create an IBMid account. If your organization uses Enterprise Federation (EF) for authentication with corporate credentials, see the IBMid EF documentation.
-
On the Download options page, select Download using your browser (HTTPS), and then click Continue.
-
Review the terms and conditions, and then click I agree to activate the download links.
-
-
Click the DSE RPM package link to download the file, for example,
dse-5.1.48-rpm.zip. -
Extract the RPM files from the
.zipfile:unzip dse-**VERSION**-rpm.zipReplace
VERSIONwith the version of DSE you downloaded, such as5.1.48.You can use the package signing public key (
dse-rpm-signing.pub.key) in the file to set up and verify the RPM packages. -
Import the package signing public key:
sudo rpm --import dse-rpm-signing.pub.key -
Set up a local Yum repository to host the downloaded RPM files:
- Apache
-
See Apachein the Red Hat documentation for more information.
- nginx
-
See nginx in the Red Hat documentation for more information.
- Red Hat Satellite
-
See Uploading content to custom RPM repositories in the Red Hat Satellite documentation for more information.
-
Add the local DataStax Yum repository to a file called
/etc/yum.repos.d/datastax.repo:[datastax] name=DataStax Repo for DSE baseurl=file:**REPOSITORY_DIRECTORY_PATH** enabled=1 gpgcheck=0 -
Install the DSE packages.
Specify all packages; otherwise, the installation fails.
-
Install the latest patch release of DSE 5.1:
sudo yum install dse-full -
Install an earlier patch release of DSE 5.1:
sudo yum install dse-5.1.version_number-1 \ dse-full-5.1.version_number-1 \ dse-libgraph-5.1.version_number-1 \ dse-libcassandra-5.1.version_number-1 \ dse-libhadoop2-client-5.1.version_number-1 \ dse-libsolr-5.1.version_number-1 \ dse-libtomcat-5.1.version_number-1 \ dse-liblog4j-5.1.version_number-1 \ dse-libspark-5.1.version_number-1For example:
sudo yum install dse-5.1.0-1 \ dse-full-5.1.0-1 \ dse-libgraph-5.1.0-1 \ dse-libcassandra-5.1.0-1 \ dse-libhadoop2-client-5.1.0-1 \ dse-libsolr-5.1.0-1 \ dse-libtomcat-5.1.0-1 \ dse-liblog4j-5.1.0-1 \ dse-libspark-5.1.0-1 -
Optional, non-production environments only: Install the demos.
Installing the DSE demos isn’t recommended for production. Only install the demos in development environments to run tutorials.
sudo yum install dse-demos-version_number-1
-
-
If needed, configure
systemdunits. -
Optional: Single-node cluster installations only:
-
If DSE is not already running:
sudo service dse startFor more start options, see Starting DSE as a service.
-
Verify that DSE is running:
nodetool statusResult using vnodesDatacenter: 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 rack1Result not using vnodesDatacenter: 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
-
-
If your DSE OpsCenter version is not compatible with DSE 5.1, upgrade DSE OpsCenter to a compatible version.
Next steps
DSE is ready for additional configuration:
-
Change or delete the default
cassandrauser created during installation. See Creating superuser accounts. -
See Configuration for DSE settings, including DSE Advanced Security, In-Memory, DSE Advanced Replication, DSE Multi-Instance, and DSE Tiered Storage.
-
Default file locations for package and Installer-Services installations