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 1.1 to Scylla 1.2, and rollback to 1.1 if required.
This guide covers upgrading Scylla from the following versions: 1.1.x to Scylla version 1.2.y, on the following platforms:
Fedora 22
Red Hat Enterprise Linux, version 7 and later
CentOS, version 7 and later
A Scylla upgrade is a rolling procedure which does not require full cluster shutdown. For each of the nodes in the cluster, serially (i.e. one at a time), you will:
backup the data
check your current release
backup configuration file
download and install new Scylla packages
gracefully restart Scylla
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 with the new version.
During the rolling upgrade it is highly recommended:
Not to use new 1.2 features
Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
Not to apply schema changes
Before any major procedure, like an upgrade, it is recommended to backup
all the data to an external device. In Scylla, backup is done using the
nodetool snapshot command. For each node in the cluster, run the
following command:
nodetool snapshot
Take note of the directory name that nodetool gives you, and copy all
the directories having this name under /var/lib/scylla to a backup
device.
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.1
sudo rm -rf /etc/yum.repos.d/scylla.repo
Before upgrading, check what version you are running now using
rpm -qa | grep scylla-server. You should use the same version in
case you want to
rollback the
upgrade. If you are not running a 1.1.x version, stop right here! This
guide only covers 1.1.x to 1.2.y upgrades.
To upgrade:
Update the Scylla RPM repo to 1.2
install
sudo yum clean all
sudo yum update scylla-server scylla-jmx scylla-tools -y
sudo yum install scylla
nodetool drain
sudo systemctl restart scylla-server.service
Check cluster status with nodetool status and make sure all
nodes, including the one you just upgraded, are in UN status.
Use journalctl _COMM=scylla to check there are no new errors in
the log.
Check again after 2 minutes, to validate no new issues are introduced.
Once you are sure the node upgrade is successful, move to the next node in the cluster.
The following procedure describes a rollback from Scylla release 1.2.x to 1.1.y. Apply this procedure if an upgrade from 1.1 to 1.2 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 1.2
Scylla rollback is a rolling procedure which does not require full cluster shutdown. For each of the nodes rollback to 1.1, you will:
retrieve the old Scylla packages
drain the node
restore the configuration file
restart Scylla
validate the rollback success
Apply the following procedure serially on each node. Do not move to the next node before validating the node is up and running with the new version.
Remove the old repo file.
sudo rm -rf /etc/yum.repos.d/scylla.repo
Update the Scylla RPM repo to 1.1
Install
sudo yum clean all
sudo yum remove scylla
sudo yum downgrade scylla-server scylla-jmx scylla-tools -y
nodetool drain
sudo service scylla-server stop
sudo rm -rf /etc/scylla/scylla.yaml
sudo cp -a /etc/scylla/scylla.yaml.backup-1.1 /etc/scylla/scylla.yaml
sudo systemctl start scylla-server.service
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
Was this page helpful?