Was this page helpful?
Caution
You're viewing documentation for a previous version of ScyllaDB Open Source. Switch to the latest stable version.
This document is a step by step procedure for upgrading from Scylla 4.5 to Scylla 4.6, and rollback to version 4.5 if required.
This guide covers upgrading Scylla 4.5 to Scylla 4.6 on Red Hat Enterprise Linux 7/8 or CentOS 7/8. See OS Support by Platform and Version for information about supported versions.
Upgrading your ScyllaDB version is a rolling procedure that does not require a full cluster shutdown. For each of the nodes in the cluster, serially (i.e. one at a time), you will:
Check the cluster’s schema
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
Apply the following procedure serially on each node. Do not move to the next node before validating the node is up and running the new version.
During the rolling upgrade, it is highly recommended:
Not to use the new 4.6 features
Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes. See sctool for suspending ScyllaDB Manager (only available for ScyllaDB Enterprise) scheduled or running repairs.
Not to apply schema changes
Note
Before upgrading, make sure to use the latest ScyllaDB Montioring stack.
Make sure that all nodes have the schema synced before the upgrade. The upgrade 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. In ScyllaDB, backup is done using the nodetool snapshot command. For each node in the cluster, run the following command:
nodetool drain
nodetool snapshot
Take note of the directory name that nodetool gives you, and copy all the directories having that name under /var/lib/scylla to an external backup device.
When the upgrade is completed on all nodes, remove the snapshot with the nodetool clearsnapshot -t <snapshot> command to prevent running out of space.
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-src
sudo systemctl stop scylla-server
docker exec -it some-scylla supervisorctl stop scylla
(without stopping some-scylla container)
Before upgrading, check what version you are running now using rpm -qa | grep scylla-server. You should use the same version as this version in case you want to rollback the upgrade. If you are not running a 4.5.x version, stop right here! This guide only covers 4.5.x to 4.6.y upgrades.
To upgrade:
Update the Scylla rpm repo to 4.6.
Install the new ScyllaDB version:
sudo yum clean all sudo yum update scylla\* -y
sudo systemctl start scylla-serverdocker exec -it some-scylla supervisorctl start scylla(with some-scylla container already running)
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.
Use journalctl _COMM=scylla to check 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.
See Scylla Metrics Update - Scylla 4.5 to 4.6 for more information..
Note
Execute the following commands one node at the time, moving to the next node only after the rollback procedure completed successfully.
The following procedure describes a rollback from Scylla release 4.6.x to 4.5.y. Apply this procedure if an upgrade from 4.5 to 4.6 failed before completing on all nodes. Use this procedure only for the nodes that you upgraded to 4.6.
ScyllaDB rollback is a rolling procedure that does not require a full cluster shutdown. For each of the nodes you rollback to 4.5, you will:
Drain the node and stop ScyllaDB
Retrieve the old ScyllaDB packages
Restore the configuration file
Reload the 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 the rollback was successful and that the node is up and running the old version.
nodetool drain
.. include:: /rst_include/scylla-commands-stop-index.rst
Remove the old repo file.
sudo rm -rf /etc/yum.repos.d/scylla.repo
Update the Scylla rpm repo to 4.5.
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
sudo rm -rf /etc/scylla/scylla.yaml
sudo cp -a /etc/scylla/scylla.yaml.backup-src | /etc/scylla/scylla.yaml
Restore all tables of system and system_schema from previous snapshot because 4.6 uses a different set of system tables. See Restore from a Backup and Incremental Backup for details.
cd /var/lib/scylla/data/keyspace_name/table_name-UUID/snapshots/<snapshot_name>/
sudo cp -r * /var/lib/scylla/data/keyspace_name/table_name-UUID/
sudo chown -R scylla:scylla /var/lib/scylla/data/keyspace_name/table_name-UUID/
You must reload the unit file if the systemd unit file is changed.
sudo systemctl daemon-reload
sudo systemctl start scylla-serverdocker exec -it some-scylla supervisorctl start scylla(with some-scylla container already running)
Check the upgrade instructions above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.