Upgrading DataStax Enterprise 4.5-5.1 using the DataStax installer
DataStax Enterprise upgrade instructions for the DataStax Installer.
Default DataStax Enterprise installer backup locations (DSE 4.5 to 5.1)
The backup directory name is based on date and time. For example: 20170212_221550Installer-Services | /usr/share/dse/backups/backup_file_dir |
Installer-No Services | install_location/backups/backup_file_dir |
cassandra.yaml
The location of the cassandra.yaml file depends on the type of installation:
Package installations |
/etc/cassandra/cassandra.yaml |
Tarball installations |
install_location/conf/cassandra.yaml |
dse.yaml
The location of the dse.yaml file depends on the type of installation:Package installations | /etc/dse/dse.yaml |
Tarball installations | installation_location/resources/dse/conf/dse.yaml |
- Drains the currently running node.
- Preserves the configuration files and places them in a backup directory.
- Removes previously installed packages.
- Updates the cassandra.yaml and dse.yaml configuration files with new entries.
Prerequisites
To upgrade to the latest version of DataStax Enterprise using the DataStax Installer, ensure the following requirements are met:
- DataStax Enterprise 4.5 or 4.6 for upgrading to 4.8
- DataStax Enterprise 4.7 or 4.8 for upgrading to 5.0
- DataStax Enterprise 5.0 for upgrading to 5.1
Upgrading Linux installations using the DataStax installer
- Familiarize yourself with the changes and features in the
release:
- DataStax Enterprise release notes for 5.1, 5.0, and 4.8.
- General upgrade advice and Cassandra features in NEWS.txt. If you are upgrading from an earlier version, read NEWS.txt all the way back to your current version.
- Cassandra changes in CHANGES.txt.
- Upgrade to the latest patch release on your current version. Fixes included in
the latest patch release can simplify the upgrade process.Get the current DSE version:
bin/dse -v current_dse_version
- Verify the Java runtime version and upgrade to the recommended version.
java -version
- DataStax Enterprise 4.7 or 4.8
-
The latest version of Oracle Java SE Runtime Environment 7 or 8 or OpenJDK 7 is recommended. The JDK is recommended for development and production systems. The JDK provides useful troubleshooting tools that are not in the JRE, such as jstack, jmap, jps, and jstat.Note: If using Oracle Java 7, you must use at least 1.7.0_25. If using Oracle Java 8, you must use at least 1.8.0_40.
- DataStax Enterprise 5.0 and later
-
The JDK is recommended for development and production systems, and provides useful troubleshooting tools that are not in the JRE, such as jstack, jmap, jps, and jstat.
- Download the installer for your computer from the DataStax downloads page or use the following command:
curl --user dsa_email_address:password -O https://downloads.datastax.com/enterprise/DataStaxEnterprise-5.1.x-linux-x64-installer.run
For example, alice can run this command to download DSE 5.1.0:curl --user alice@email.com:password -O https://downloads.datastax.com/enterprise/DataStaxEnterprise-5.1.0-linux-x64-installer.run
- From the directory where you downloaded the install file, make it executable and run it
using the sudo
command.
$ chmod +x DataStaxEnterprise-version_number-linux-x64-installer.run ## Changes permission to executable $ sudo ./DataStaxEnterprise-version_number-linux-x64-installer.run
- Follow the instructions in the setup wizard. For a detailed description of the settings in the wizard, see the installation instructions in 5.1, 5.0, or 4.8.
- When upgrading DSE to versions earlier than
5.1.16, 6.0.8, or 6.7.4 inclusive, if any tables are using DSE Tiered Storage,
remove all
txn_compaction
log files from second-level tiers and lower. For example, given the following dse.yaml configuration, removetxn_compaction
log files from/mnt2
and/mnt3
directories:tiered_storage_options: strategy1: tiers: - paths: - /mnt1 - paths: - /mnt2 - paths: - /mnt3
The following example removes the files using the find command:
find /mnt2 -name "*_txn_compaction_*.log" -type f -delete && find /mnt3 -name "*_txn_compaction_*.log" -type f -delete
Warning: Failure to complete this step may result in data loss. - Start DataStax
Enterprise:
sudo service dse start ## Starts the DataStax Enterprise server
- (DataStax Enterprise 4.7 and 4.8 only) Start the DataStax Agent:
sudo service datastax-agent start
Note: For DataStax Enterprise 5.0, see the OpsCenter 6.0 documentation. For DataStax Enterprise 5.1, see the OpsCenter 6.1 documentation. - Verify that DataStax Enterprise is
running:
nodetool status