Was this page helpful?
This document is a step by step procedure for upgrading from ScyllaDB Enterprise 2022.2 to ScyllaDB Enterprise 2024.1, and rollback to version 2022.2 if required.
This guide covers upgrading ScyllaDB on Red Hat Enterprise Linux (RHEL) CentOS, Debian, and Ubuntu. See OS Support by Platform and Version for information about supported versions.
This guide also applies when you’re upgrading ScyllaDB Enterprise official image on EC2, GCP, or Azure.
Upgrade Your Driver
If you’re using a ScyllaDB driver, upgrade the driverbefore you upgrade ScyllaDB Enterprise. The latest two versions of each driver are supported.
Upgrade ScyllaDB Monitoring Stack
If you’re using the ScyllaDB Monitoring Stack, verify that your Monitoring Stack version supports the ScyllaDB Enterprise version to which you want to upgrade. See ScyllaDB Monitoring Stack Support Matrix. We recommend upgrading the Monitoring Stack to the latest version.
Note
DateTieredCompactionStrategy is removed in 2024.1. Migrate to TimeWindowCompactionStrategy before you upgrade from 2022.2 to 2024.1.
Note
In ScyllaDB Enterprise 2024.1, Raft-based consistent cluster management for existing deployments is enabled by default. If you want the consistent cluster management feature to be disabled in version 2024.1, you must update the configuration before upgrading from 2022.2 to 2024.1:
Set
consistent_cluster_management: falsein thescylla.yamlconfiguration file on each node in the cluster.Start the upgrade procedure.
A ScyllaDB upgrade is a rolling procedure which does not require full cluster shutdown. For each of the nodes in the cluster you will:
Check that the cluster’s schema is synchronized
Drain the node and backup the data
Backup the configuration file
Stop ScyllaDB
Download and install new ScyllaDB packages
Start ScyllaDB
Validate that the upgrade was successful
Caution
Apply the procedure serially on each node. Do not move to the next node before validating that the node you upgraded is up and running the new version.
During the rolling upgrade, you should NOT:
Use the new 2024.1 features.
Run administration functions, like repairs, refresh, rebuild or add or remove nodes. See sctool for suspending ScyllaDB Manager’s scheduled or running repairs.
Apply schema changes.
After the upgrade, you need to verify that Raft was successfully enabled
in your cluster. You can skip this step only if you disabled the consistent_cluster_management
option before upgrading to version 2024.1, as described in the note in
the Before You Upgrade ScyllaDB section.
Otherwise, as soon as every node has been upgraded to the new version, the cluster will start a procedure that initializes the Raft algorithm for consistent cluster metadata management. You must then verify that the Raft initialization procedure has successfully finished.
Make sure that all nodes have the schema synchronized before upgrade. The upgrade procedure will fail if there is a schema disagreement between nodes.
nodetool describecluster
Before any major procedure, like an upgrade, it is recommended to backup all the data to an external device. You can use ScyllaDB Manager for creating backups.
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-src
sudo service scylla-server stop
Before upgrading, check what version you are running now using scylla --version.
You should use the same version as this version in case you want to rollback
the upgrade. If you are not running a 2022.2.x version, stop right here.
This guide only covers 2022.2.x to 2024.1.y upgrades.
To upgrade ScyllaDB Enterprise:
Update the ScyllaDB deb repo (Debian, Ubuntu) to 2024.1 and and enable scylla/ppa repo:
sudo add-apt-repository -y ppa:scylladb/ppa
Configure Java 1.8:
sudo apt-get update sudo apt-get install -y openjdk-8-jre-headless sudo update-java-alternatives -s java-1.8.0-openjdk-amd64
Install the new ScyllaDB version:
sudo apt-get clean all sudo apt-get update sudo apt-get dist-upgrade scylla-enterprise
Answer ‘y’ to the first two questions.
Installing the New Version on Cloud
If you’re using the ScyllaDB official image (recommended), see the EC2/GCP/Azure Ubuntu Image tab for upgrade instructions. If you’re using your own image and installed ScyllaDB packages for Ubuntu or Debian, you need to apply an extended upgrade procedure:
Update the ScyllaDB deb repo (see above).
Configure Java 1.8 (see above).
Install the new ScyllaDB version with the additional
scylla-enterprise-machine-image package:
sudo apt-get clean all sudo apt-get update sudo apt-get dist-upgrade scylla-enterprise sudo apt-get dist-upgrade scylla-enterprise-machine-image
Run scylla_setup without running io_setup.
Run sudo /opt/scylladb/scylla-machine-image/scylla_cloud_io_setup.
To upgrade ScyllaDB Enterprise:
Update the ScyllaDB rpm repo to 2024.1.
Install the new ScyllaDB version:
sudo yum clean all sudo yum update scylla\* -y
Installing the New Version on Cloud
If you’re using the ScyllaDB official image (recommended), see the EC2/GCP/Azure Ubuntu Image tab for upgrade instructions. If you’re using your own image and installed ScyllaDB packages for CentOS/RHEL, you need to apply an extended upgrade procedure:
Update the ScyllaDB deb repo (see above).
Install the new ScyllaDB version with the additional
scylla-enterprise-machine-image package:
sudo yum clean all sudo yum update scylla\* -y sudo yum update scylla-enterprise-machine-image
Run scylla_setup without running io_setup.
Run sudo /opt/scylladb/scylla-machine-image/scylla_cloud_io_setup.
Note
If you are running a ScyllaDB Enterprise official image (for EC2 AMI, GCP, or Azure), you need to download and install the new ScyllaDB Enterprise release for Ubuntu. See Upgrade ScyllaDB Image for more information.
sudo service scylla-server start
Check cluster status with nodetool status and make sure all nodes,
including the one you just upgraded, are in UN status.
Use curl -X GET "http://localhost:10000/storage_service/scylla_release_version"
to check the ScyllaDB version. Validate that the version matches the one you upgraded to.
Check scylla-server log (using journalctl _COMM=scylla) and /var/log/syslog
to validate there are no new errors in the log.
Check again after two minutes, to validate no new issues are introduced.
Once you are sure the node upgrade was successful, move to the next node in the cluster.
This section applies to upgrades where Raft is initialized for the first time in the cluster, which in 2024.1 happens by default.
You can skip this section only if you disabled the consistent_cluster_management
option before upgrading to 2024.1, as described in the note in
the Before You Upgrade ScyllaDB section (i.e., you prevented Raft from being
enabled in 2024.1).
Enabling Raft causes the ScyllaDB cluster to start an internal Raft initialization procedure as soon as every node is upgraded to the new version. The goal of that procedure is to initialize data structures used by the Raft algorithm to consistently manage cluster-wide metadata, such as table schemas.
Assuming you performed the rolling upgrade procedure correctly (in particular, ensuring that the schema is synchronized on every step), and if there are no problems with cluster connectivity, that internal procedure should take a few seconds to finish. However, the procedure requires full cluster availability. If one of the nodes fails before the procedure finishes (for example, due to a hardware problem), the process may get stuck, which may prevent schema or topology changes in your cluster.
Therefore, following the rolling upgrade, you must verify that the internal Raft initialization procedure has finished successfully by checking the logs of every ScyllaDB node. If the process gets stuck, manual intervention is required.
Refer to the Verifying that the internal Raft upgrade procedure finished successfully section for instructions on verifying that the procedure was successful and proceeding if it gets stuck.
Note
Execute the following commands one node at a time, moving to the next node only after the rollback procedure is completed successfully.
The following procedure describes a rollback from ScyllaDB Enterprise 2024.1.x to 2022.2.y. Apply this procedure if an upgrade from 2022.2 to 2024.1 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2024.1.
Warning
The rollback procedure can be applied only if some nodes have not been upgraded to 2024.1 yet. As soon as the last node in the rolling upgrade procedure is started with 2024.1, rollback becomes impossible. At that point, the only way to restore a cluster to 2022.2 is by restoring it from backup.
ScyllaDB rollback is a rolling procedure which does not require a full cluster shutdown. For each of the nodes you rollback to 2022.2 you will:
Drain the node and stop ScyllaDB
Retrieve the old ScyllaDB packages
Restore the configuration file
Restore system tables
Reload systemd configuration
Restart ScyllaDB
Validate the rollback success
Apply the following procedure serially on each node. Do not move to the next node before validating that the rollback was successful and the node is up and running the old version.
nodetool drain
sudo service scylla-server stop
Remove the old repo file.
sudo rm -rf /etc/apt/sources.list.d/scylla.list
Install:
sudo apt-get update sudo apt-get remove scylla\* -y sudo apt-get install scylla-enterprise
Answer ‘y’ to the first two questions.
Remove the old repo file.
sudo rm -rf /etc/yum.repos.d/scylla.repo
Update the ScyllaDB rpm repo to 2022.2.
Install:
sudo yum clean all sudo rm -rf /var/cache/yum sudo yum remove scylla\*tools-core sudo yum downgrade scylla\* -y sudo yum install scylla-enterprise
Note
If you are running a ScyllaDB Enterprise official image (for EC2 AMI, GCP, or Azure), follow the instructions for Ubuntu.
sudo rm -rf /etc/scylla/scylla.yaml
sudo cp -a /etc/scylla/scylla.yaml.backup-src | /etc/scylla/scylla.yaml
You must reload the unit file if the systemd unit file is changed.
sudo systemctl daemon-reload
sudo service scylla-server start
Check the upgrade instructions above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.