Compare commits
6 Commits
copilot/fi
...
scylla-5.4
| Author | SHA1 | Date | |
|---|---|---|---|
|
24efacf90d | ||
|
1639a468df | ||
|
a0766ac236 | ||
|
fa0f382a82 | ||
|
|
37fd8a4c36 | ||
|
83f7d0073a |
@@ -78,7 +78,7 @@ fi
|
||||
|
||||
# Default scylla product/version tags
|
||||
PRODUCT=scylla
|
||||
VERSION=5.4.0-dev
|
||||
VERSION=5.4.0-rc1
|
||||
|
||||
if test -f version
|
||||
then
|
||||
|
||||
@@ -1888,6 +1888,7 @@ future<> system_keyspace::make(
|
||||
replica::database& db) {
|
||||
for (auto&& table : system_keyspace::all_tables(db.get_config())) {
|
||||
co_await db.create_local_system_table(table, maybe_write_in_user_memory(table), erm_factory);
|
||||
co_await db.find_column_family(table).init_storage();
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
@@ -91,7 +91,7 @@ redirects: setup
|
||||
# Preview commands
|
||||
.PHONY: preview
|
||||
preview: setup
|
||||
$(POETRY) run sphinx-autobuild -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml --host $(PREVIEW_HOST) --port 5500 --ignore '_data/*'
|
||||
$(POETRY) run sphinx-autobuild -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml --host $(PREVIEW_HOST) --port 5500 --ignore *.csv --ignore *.yaml
|
||||
|
||||
.PHONY: multiversionpreview
|
||||
multiversionpreview: multiversion
|
||||
|
||||
@@ -118,6 +118,7 @@ class AMIVersionsTemplateDirective(Directive):
|
||||
option_spec = {
|
||||
"version": directives.unchanged,
|
||||
"exclude": directives.unchanged,
|
||||
"only_latest": directives.flag,
|
||||
}
|
||||
|
||||
def _extract_version_from_filename(self, filename):
|
||||
@@ -169,6 +170,8 @@ class AMIVersionsTemplateDirective(Directive):
|
||||
LOGGER.warning(
|
||||
f"No files match in directory '{download_directory}' with version pattern '{version_pattern}'."
|
||||
)
|
||||
elif "only_latest" in self.options:
|
||||
files = [files[0]]
|
||||
|
||||
output = []
|
||||
for file in files:
|
||||
|
||||
@@ -1,2 +1,107 @@
|
||||
### a dictionary of redirections
|
||||
#old path: new path
|
||||
#old path: new path
|
||||
|
||||
|
||||
# Removed the outdated upgrade guides
|
||||
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-ubuntu-14-to-16.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.x.y-to-2.x.z/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.x.y-to-2.x.z/upgrade-guide-from-2.x.y-to-2.x.z-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.x.y-to-2.x.z/upgrade-guide-from-2.x.y-to-2.x.z-ubuntu.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.x.y-to-2.x.z/upgrade-guide-from-2.x.y-to-2.x.z-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.1-to-2.2/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.1-to-2.2/upgrade-guide-from-2.1-to-2.2-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.1-to-2.2/upgrade-guide-from-2.1-to-2.2-ubuntu.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.1-to-2.2/upgrade-guide-from-2.1-to-2.2-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.1-to-2.2/metric-update-2.1-to-2.2.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.2-to-2.3/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.2-to-2.3/upgrade-guide-from-2.2-to-2.3-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.2-to-2.3/upgrade-guide-from-2.2-to-2.3-ubuntu.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.2-to-2.3/upgrade-guide-from-2.2-to-2.3-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.2-to-2.3/upgrade-guide-from-2.2-to-2.3-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.2-to-2.3/metric-update-2.2-to-2.3.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/upgrade-guide-from-2.3-to-3.0-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/upgrade-guide-from-2.3-to-3.0-ubuntu.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/upgrade-guide-from-2.3-to-3.0-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/upgrade-guide-from-2.3-to-3.0-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/upgrade-guide-from-2.3-to-3.0-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/metric-update-2.3-to-3.0.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.0-to-3.1/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.0-to-3.1/upgrade-guide-from-3.0-to-3.1-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.0-to-3.1/upgrade-guide-from-3.0-to-3.1-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.0-to-3.1/upgrade-guide-from-3.0-to-3.1-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.0-to-3.1/upgrade-guide-from-3.0-to-3.1-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.0-to-3.1/metric-update-3.0-to-3.1.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.1-to-3.2/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.1-to-3.2/upgrade-guide-from-3.1-to-3.2-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.1-to-3.2/upgrade-guide-from-3.1-to-3.2-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.1-to-3.2/upgrade-guide-from-3.1-to-3.2-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.1-to-3.2/upgrade-guide-from-3.1-to-3.2-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.1-to-3.2/metric-update-3.1-to-3.2.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.2-to-3.3/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.2-to-3.3/upgrade-guide-from-3.2-to-3.3-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.2-to-3.3/upgrade-guide-from-3.2-to-3.3-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.2-to-3.3/upgrade-guide-from-3.2-to-3.3-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.2-to-3.3/upgrade-guide-from-3.2-to-3.3-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.2-to-3.3/metric-update-3.2-to-3.3.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.3-to-4.0/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.3-to-4.0/upgrade-guide-from-3.3-to-4.0-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.3-to-4.0/upgrade-guide-from-3.3-to-4.0-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.3-to-4.0/upgrade-guide-from-3.3-to-4.0-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.3-to-4.0/upgrade-guide-from-3.3-to-4.0-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.3-to-4.0/metric-update-3.3-to-4.0.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.x.y-to-3.x.z/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.x.y-to-3.x.z/upgrade-guide-from-3.x.y-to-3.x.z-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.x.y-to-3.x.z/upgrade-guide-from-3.x.y-to-3.x.z-ubuntu.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-3.x.y-to-3.x.z/upgrade-guide-from-3.x.y-to-3.x.z-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/upgrade-guide-from-4.0-to-4.1-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/upgrade-guide-from-4.0-to-4.1-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/upgrade-guide-from-4.0-to-4.1-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/upgrade-guide-from-4.0-to-4.1-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/alternator.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/metric-update-4.0-to-4.1.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.x.y-to-4.x.z/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.x.y-to-4.x.z/upgrade-guide-from-4.x.y-to-4.x.z-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.x.y-to-4.x.z/upgrade-guide-from-4.x.y-to-4.x.z-ubuntu.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.x.y-to-4.x.z/upgrade-guide-from-4.x.y-to-4.x.z-debian.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.1-to-4.2/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.1-to-4.2/upgrade-guide-from-4.1-to-4.2-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.1-to-4.2/upgrade-guide-from-4.1-to-4.2-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.1-to-4.2/upgrade-guide-from-4.1-to-4.2-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.1-to-4.2/upgrade-guide-from-4.1-to-4.2-debian-9.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.1-to-4.2/upgrade-guide-from-4.1-to-4.2-debian-10.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.1-to-4.2/metric-update-4.1-to-4.2.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.2-to-4.3/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.2-to-4.3/upgrade-guide-from-4.2-to-4.3-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.2-to-4.3/upgrade-guide-from-4.2-to-4.3-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.2-to-4.3/upgrade-guide-from-4.2-to-4.3-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.2-to-4.3/upgrade-guide-from-4.2-to-4.3-debian-9.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.2-to-4.3/upgrade-guide-from-4.2-to-4.3-debian-10.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.2-to-4.3/metric-update-4.2-to-4.3.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.3-to-4.4/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.3-to-4.4/upgrade-guide-from-4.3-to-4.4-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.3-to-4.4/upgrade-guide-from-4.3-to-4.4-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.3-to-4.4/upgrade-guide-from-4.3-to-4.4-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.3-to-4.4/upgrade-guide-from-4.3-to-4.4-ubuntu-20-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.3-to-4.4/upgrade-guide-from-4.3-to-4.4-debian-9.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.3-to-4.4/upgrade-guide-from-4.3-to-4.4-debian-10.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.3-to-4.4/metric-update-4.3-to-4.4.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.4-to-4.5/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.4-to-4.5/upgrade-guide-from-4.4-to-4.5-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.4-to-4.5/upgrade-guide-from-4.4-to-4.5-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.4-to-4.5/upgrade-guide-from-4.4-to-4.5-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.4-to-4.5/upgrade-guide-from-4.4-to-4.5-ubuntu-20-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.4-to-4.5/upgrade-guide-from-4.4-to-4.5-debian-9.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.4-to-4.5/upgrade-guide-from-4.4-to-4.5-debian-10.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.4-to-4.5/metric-update-4.4-to-4.5.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.5-to-4.6/index.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.5-to-4.6/upgrade-guide-from-4.5-to-4.6-rpm.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.5-to-4.6/upgrade-guide-from-4.5-to-4.6-ubuntu-16-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.5-to-4.6/upgrade-guide-from-4.5-to-4.6-ubuntu-18-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.5-to-4.6/upgrade-guide-from-4.5-to-4.6-ubuntu-20-04.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.5-to-4.6/upgrade-guide-from-4.5-to-4.6-debian-9.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.5-to-4.6/upgrade-guide-from-4.5-to-4.6-debian-10.html: /stable/upgrade/index.html
|
||||
/stable/upgrade/upgrade-opensource/upgrade-guide-from-4.5-to-4.6/metric-update-4.5-to-4.6.html: /stable/upgrade/index.html
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
==========
|
||||
AWS images
|
||||
AWS Images
|
||||
==========
|
||||
|
||||
.. scylladb_aws_images_template::
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
========================
|
||||
Configuration parameters
|
||||
Configuration Parameters
|
||||
========================
|
||||
|
||||
This section contains a list of properties that can be configured in ``scylla.yaml`` - the main configuration file for ScyllaDB.
|
||||
|
||||
@@ -3,7 +3,7 @@ Reference
|
||||
===============
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:maxdepth: 1
|
||||
:glob:
|
||||
|
||||
/reference/*
|
||||
@@ -1,170 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 1.6 to 1.7 for |OS|
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.6 to Scylla 1.7, and rollback to 1.6 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 1.6.x to Scylla version 1.7.y on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* drain node and backup the data
|
||||
* check your current release
|
||||
* backup configuration file
|
||||
* stop Scylla
|
||||
* download and install new Scylla packages
|
||||
* start 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.7 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.6
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a 1.6.x version, stop right here! This guide only covers 1.6.x to 1.7.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |APT|_ to **1.7**
|
||||
2. Upgrade java to 1.8 on Ubuntu 14.04 and Debian 8, which is requested by Scylla 1.7
|
||||
|
||||
* |ENABLE_APT_REPO|
|
||||
* sudo apt-get update
|
||||
* sudo apt-get install -y |JESSIE_BACKPORTS|
|
||||
* sudo update-java-alternatives -s java-1.8.0-openjdk-amd64
|
||||
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04 and Debian 8) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.7.x to 1.6.y. Apply this procedure if an upgrade from 1.6 to 1.7 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 1.7
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 1.6, you will:
|
||||
|
||||
* drain the node and stop Scylla
|
||||
* retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the |APT|_ to **1.6**
|
||||
3. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla\* -y
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.6 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,190 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 1.7 to 2.0 for |OS|
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.7 to Scylla 2.0, and rollback to 1.7 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 1.7.x (x >= 4) to Scylla version 2.0.y on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* check cluster schema
|
||||
* drain node and backup the data
|
||||
* backup configuration file
|
||||
* stop Scylla
|
||||
* download and install new Scylla packages
|
||||
* start 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 2.0 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.7
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a 1.7.x version, stop right here! This guide only covers 1.7.x to 2.0.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |APT|_ to **2.0**
|
||||
2. Upgrade java to 1.8 on Ubuntu 14.04 and Debian 8, which is requested by Scylla 2.0
|
||||
|
||||
* |ENABLE_APT_REPO|
|
||||
* sudo apt-get update
|
||||
* sudo apt-get install -y |JESSIE_BACKPORTS|
|
||||
* sudo update-java-alternatives -s java-1.8.0-openjdk-amd64
|
||||
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04 and Debian 8) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
* More on :doc:`Scylla Metrics Update - Scylla 1.7 to 2.0<metric-update-1.7-to-2.0>`
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 2.0.x to 1.7.y (y >= 4). Apply this procedure if an upgrade from 1.7 to 2.0 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2.0
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 1.7, you will:
|
||||
|
||||
* drain the node and stop Scylla
|
||||
* retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the |APT|_ to **1.7**
|
||||
3. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla\* -y
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.7 /etc/scylla/scylla.yaml
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, 2.0 uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,157 +0,0 @@
|
||||
======================================================================
|
||||
Upgrade Guide - Scylla 1.x.y to 1.x.z for |OS|
|
||||
======================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.x.y to Scylla 1.x.z.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 1.x.y to Scylla version 1.x.z on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* drain node and backup the data
|
||||
* check your current release
|
||||
* backup configuration file and deb packages
|
||||
* stop Scylla
|
||||
* download and install new Scylla packages
|
||||
* start 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.x.z features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file and deb packages
|
||||
------------------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.x.z
|
||||
|
||||
If you install scylla by apt, you can find the deb packages in ``/var/cache/apt/``, backup them to ``scylla_1.x.y_backup`` directory which will be used in rollback.
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a 1.x.y version, stop right here! This guide only covers 1.x.y to 1.x.z upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |APT|_ to **1.x**
|
||||
2. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.x.z to 1.x.y. Apply this procedure if an upgrade from 1.x.y to 1.x.z failed before completing on all nodes. Use this procedure only for nodes you upgraded to 1.x.z
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 1.x.y, you will:
|
||||
|
||||
* drain the node and stop Scylla
|
||||
* retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
Install the old release from backuped deb packages
|
||||
--------------------------------------------------
|
||||
1. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get remove scylla\* -y
|
||||
sudo apt-get install scylla_1.x.y_backup/scylla*.deb
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.x.z /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,201 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 2.0 to 2.1 for |OS|
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 2.0 to Scylla 2.1, and rollback to 2.0 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 2.0.x to Scylla version 2.1.y on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 2.1 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-2.0
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a 2.0.x version, stop right here! This guide only covers 2.0.x to 2.1.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |APT|_ to **2.1**, and enable scylla/ppa repo
|
||||
|
||||
.. code:: sh
|
||||
|
||||
Debian 8:
|
||||
sudo apt-get install gnupg-curl -y
|
||||
sudo apt-key adv --fetch-keys https://download.opensuse.org/repositories/home:/scylladb:/scylla-3rdparty-jessie/Debian_8.0/Release.key
|
||||
sudo sh -c "echo 'deb http://download.opensuse.org/repositories/home:/scylladb:/scylla-3rdparty-jessie/Debian_8.0/ /' > /etc/apt/sources.list.d/scylla-3rdparty.list"
|
||||
|
||||
Ubuntu 14/16:
|
||||
sudo add-apt-repository -y ppa:scylladb/ppa
|
||||
|
||||
2. Upgrade java to 1.8 on Ubuntu 14.04 and Debian 8, which is requested by Scylla 2.1
|
||||
|
||||
* |ENABLE_APT_REPO|
|
||||
* sudo apt-get update
|
||||
* sudo apt-get install -y |JESSIE_BACKPORTS|
|
||||
* sudo update-java-alternatives -s java-1.8.0-openjdk-amd64
|
||||
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04 and Debian 8) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
* More on :doc:`Scylla Metrics Update - Scylla 2.0 to 2.1<metric-update-2.0-to-2.1>`
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 2.1.x to 2.0.y. Apply this procedure if an upgrade from 2.0 to 2.1 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2.1
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 2.0, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the |APT|_ to **2.0**
|
||||
3. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla\* -y
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-2.0 /etc/scylla/scylla.yaml
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, 2.1 uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,200 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 2.1 to 2.2 for |OS|
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 2.1 to Scylla 2.2, and rollback to 2.1 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 2.1.x to Scylla version 2.2.y on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 2.2 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
for conf in $(cat /var/lib/dpkg/info/scylla-*server.conffiles /var/lib/dpkg/info/scylla-*conf.conffiles /var/lib/dpkg/info/scylla-*jmx.conffiles | grep -v init ); do sudo cp -v $conf $conf.backup-2.1; done
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a 2.1.x version, stop right here! This guide only covers 2.1.x to 2.2.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |APT|_ to **2.2**, and enable scylla/ppa repo
|
||||
|
||||
.. code:: sh
|
||||
|
||||
Debian 8:
|
||||
sudo apt-get install gnupg-curl -y
|
||||
sudo apt-key adv --fetch-keys https://download.opensuse.org/repositories/home:/scylladb:/scylla-3rdparty-jessie/Debian_8.0/Release.key
|
||||
sudo sh -c "echo 'deb http://download.opensuse.org/repositories/home:/scylladb:/scylla-3rdparty-jessie/Debian_8.0/ /' > /etc/apt/sources.list.d/scylla-3rdparty.list"
|
||||
|
||||
Ubuntu 14/16:
|
||||
sudo add-apt-repository -y ppa:scylladb/ppa
|
||||
|
||||
2. Upgrade java to 1.8 on Ubuntu 14.04 and Debian 8, which is requested by Scylla 2.2
|
||||
|
||||
* |ENABLE_APT_REPO|
|
||||
* sudo apt-get update
|
||||
* sudo apt-get install -y |JESSIE_BACKPORTS|
|
||||
* sudo update-java-alternatives -s java-1.8.0-openjdk-amd64
|
||||
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04 and Debian 8) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
* More on :doc:`Scylla Metrics Update - Scylla 2.1 to 2.2<metric-update-2.1-to-2.2>`
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 2.2.x to 2.1.y. Apply this procedure if an upgrade from 2.1 to 2.2 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2.2
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 2.1, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the |APT|_ to **2.1**
|
||||
3. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla\* -y
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
for conf in $(cat /var/lib/dpkg/info/scylla-*server.conffiles /var/lib/dpkg/info/scylla-*conf.conffiles /var/lib/dpkg/info/scylla-*jmx.conffiles | grep -v init ); do sudo cp -v $conf.backup-2.1 $conf; done
|
||||
sudo systemctl daemon-reload (Ubuntu 16.04 and Debian 8)
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, 2.2 uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,203 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 2.2 to 2.3 for |OS|
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 2.2 to Scylla 2.3, and rollback to 2.2 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 2.2.x to Scylla version 2.3.y on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 2.3 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
for conf in $(cat /var/lib/dpkg/info/scylla-*server.conffiles /var/lib/dpkg/info/scylla-*conf.conffiles /var/lib/dpkg/info/scylla-*jmx.conffiles | grep -v init ); do sudo cp -v $conf $conf.backup-2.2; done
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a 2.2.x version, stop right here! This guide only covers 2.2.x to 2.3.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |APT|_ to **2.3**, and enable scylla/ppa repo
|
||||
|
||||
.. code:: sh
|
||||
|
||||
Debian 8:
|
||||
sudo apt-get install gnupg-curl -y
|
||||
sudo apt-key adv --fetch-keys https://download.opensuse.org/repositories/home:/scylladb:/scylla-3rdparty-jessie/Debian_8.0/Release.key
|
||||
sudo sh -c "echo 'deb http://download.opensuse.org/repositories/home:/scylladb:/scylla-3rdparty-jessie/Debian_8.0/ /' > /etc/apt/sources.list.d/scylla-3rdparty.list"
|
||||
|
||||
Ubuntu 14/16:
|
||||
sudo add-apt-repository -y ppa:scylladb/ppa
|
||||
|
||||
2. Upgrade java to 1.8 on Ubuntu 14.04 and Debian 8, which is requested by Scylla 2.3
|
||||
|
||||
* |ENABLE_APT_REPO|
|
||||
* sudo apt-get update
|
||||
* sudo apt-get install -y |JESSIE_BACKPORTS|
|
||||
* sudo update-java-alternatives -s java-1.8.0-openjdk-amd64
|
||||
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04 and Debian 8) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
* More on :doc:`Scylla Metrics Update - Scylla 2.2 to 2.3<metric-update-2.2-to-2.3>`
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 2.3.x to 2.2.y. Apply this procedure if an upgrade from 2.2 to 2.3 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2.3
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 2.2, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
|
||||
|
||||
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the |APT|_ to **2.2**
|
||||
3. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla\* -y
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
for conf in $(cat /var/lib/dpkg/info/scylla-*server.conffiles /var/lib/dpkg/info/scylla-*conf.conffiles /var/lib/dpkg/info/scylla-*jmx.conffiles | grep -v init ); do sudo cp -v $conf.backup-2.2 $conf; done
|
||||
sudo systemctl daemon-reload (Ubuntu 16.04 and Debian 8)
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, 2.3 uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,218 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 2.3 to 3.0 for |OS|
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 2.3 to Scylla 3.0, and rollback to 2.3 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 2.3.x to Scylla version 3.0.y on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 3.0 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
for conf in $(cat /var/lib/dpkg/info/scylla-*server.conffiles /var/lib/dpkg/info/scylla-*conf.conffiles /var/lib/dpkg/info/scylla-*jmx.conffiles | grep -v init ); do sudo cp -v $conf $conf.backup-2.3; done
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a 2.3.x version, stop right here! This guide only covers 2.3.x to 3.0.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |APT|_ to **3.0**, and enable scylla/ppa repo
|
||||
|
||||
.. code:: sh
|
||||
|
||||
Debian 8:
|
||||
sudo apt-get install gnupg-curl -y
|
||||
sudo apt-key adv --fetch-keys https://download.opensuse.org/repositories/home:/scylladb:/scylla-3rdparty-jessie/Debian_8.0/Release.key
|
||||
sudo sh -c "echo 'deb http://download.opensuse.org/repositories/home:/scylladb:/scylla-3rdparty-jessie/Debian_8.0/ /' > /etc/apt/sources.list.d/scylla-3rdparty.list"
|
||||
|
||||
Ubuntu 14/16:
|
||||
sudo add-apt-repository -y ppa:scylladb/ppa
|
||||
|
||||
2. Upgrade java to 1.8 on Ubuntu 14.04 and Debian 8, which is requested by Scylla 3.0
|
||||
|
||||
* |ENABLE_APT_REPO|
|
||||
* sudo apt-get update
|
||||
* sudo apt-get install -y |JESSIE_BACKPORTS|
|
||||
* sudo update-java-alternatives -s java-1.8.0-openjdk-amd64
|
||||
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
4. Upgrade node_exporter
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service node_exporter stop
|
||||
sudo rm /usr/bin/node_exporter
|
||||
sudo node_exporter_install
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04 and Debian 8) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
* More on :doc:`Scylla Metrics Update - Scylla 2.3 to 3.0<metric-update-2.3-to-3.0>`
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 3.0.x to 2.3.y. Apply this procedure if an upgrade from 2.3 to 3.0 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 3.0
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 2.3, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the |APT|_ to **2.3**
|
||||
3. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla\* -y
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
for conf in $(cat /var/lib/dpkg/info/scylla-*server.conffiles /var/lib/dpkg/info/scylla-*conf.conffiles /var/lib/dpkg/info/scylla-*jmx.conffiles | grep -v init ); do sudo cp -v $conf.backup-2.3 $conf; done
|
||||
sudo systemctl daemon-reload (Ubuntu 16.04 and Debian 8)
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, 3.0 uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Install old node_exporter
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service node_exporter stop
|
||||
sudo rm /usr/bin/node_exporter
|
||||
sudo node_exporter_install
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,155 +0,0 @@
|
||||
======================================================================
|
||||
Upgrade Guide - Scylla 2.x.y to 2.x.z for |OS|
|
||||
======================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 2.x.y to Scylla 2.x.z.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 2.x.y to Scylla version 2.x.z on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* Drain node and backup the data
|
||||
* Check your current release
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 2.x.z features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-2.x.z
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a 2.x.y version, stop right here! This guide only covers 2.x.y to 2.x.z upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |APT|_ to **2.x**
|
||||
2. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 2.x.z to 2.x.y. Apply this procedure if an upgrade from 2.x.y to 2.x.z failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2.x.z
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 2.x.y, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Downgrade to previous release
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
Downgrade to previous release
|
||||
-----------------------------
|
||||
1. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get install scylla=2.x.y\* scylla-server=2.x.y\* scylla-jmx=2.x.y\* scylla-tools=2.x.y\* scylla-tools-core=2.x.y\* scylla-kernel-conf=2.x.y\* scylla-conf=2.x.y\*
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-2.x.z /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,161 +0,0 @@
|
||||
======================================================================
|
||||
Upgrade Guide - Scylla 3.x.y to 3.x.z for |OS|
|
||||
======================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 3.x.y to Scylla 3.x.z.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 3.x.y to Scylla version 3.x.z on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
.. include:: /upgrade/_common/note-ubuntu14.rst
|
||||
|
||||
.. include:: /upgrade/upgrade-opensource/upgrade-guide-from-3.x.y-to-3.x.z/_common/note_3.1.0_to_3.1.1.rst
|
||||
|
||||
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* Drain node and backup the data
|
||||
* Check your current release
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 3.x.z features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-3.x.z
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a 3.x.y version, stop right here! This guide only covers 3.x.y to 3.x.z upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |APT|_ to **3.x**
|
||||
2. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04 and Ubuntu 18.04) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 3.x.z to 3.x.y. Apply this procedure if an upgrade from 3.x.y to 3.x.z failed before completing on all nodes. Use this procedure only for nodes you upgraded to 3.x.z
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 3.x.y, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Downgrade to previous release
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
Downgrade to previous release
|
||||
-----------------------------
|
||||
1. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get install scylla=3.x.y\* scylla-server=3.x.y\* scylla-jmx=3.x.y\* scylla-tools=3.x.y\* scylla-tools-core=3.x.y\* scylla-kernel-conf=3.x.y\* scylla-conf=3.x.y\*
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-3.x.z /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,158 +0,0 @@
|
||||
======================================================================
|
||||
Upgrade Guide - ScyllaDB |FROM| to |TO| for |OS|
|
||||
======================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla |FROM| to Scylla |TO|.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: |FROM| to Scylla version |TO| on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
.. include:: /upgrade/_common/note-ubuntu14.rst
|
||||
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* Drain node and backup the data
|
||||
* Check your current release
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 |TO| features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-4.x.z
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a |FROM| version, stop right here! This guide only covers |FROM| to |TO| upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |APT|_ to **4.x**
|
||||
2. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04 and Ubuntu 18.04) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release |TO| to |FROM|. Apply this procedure if an upgrade from |FROM| to |TO| failed before completing on all nodes. Use this procedure only for nodes you upgraded to |TO|.
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to |FROM|, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Downgrade to previous release
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
Downgrade to previous release
|
||||
-----------------------------
|
||||
1. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get install scylla=4.x.y\* scylla-server=4.x.y\* scylla-jmx=4.x.y\* scylla-tools=4.x.y\* scylla-tools-core=4.x.y\* scylla-kernel-conf=4.x.y\* scylla-conf=4.x.y\*
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-4.x.z /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,183 +0,0 @@
|
||||
=============================================================================================================
|
||||
Upgrade Guide - |SCYLLA_NAME| |SRC_VERSION| to |NEW_VERSION| for Red Hat Enterprise Linux 7 or CentOS 7
|
||||
=============================================================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from |SCYLLA_NAME| |SRC_VERSION| to |SCYLLA_NAME| |NEW_VERSION|, and rollback to |SRC_VERSION| if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: |SRC_VERSION|.x or later to |SCYLLA_NAME| version |NEW_VERSION|.y, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 |NEW_VERSION| features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes. See `sctool <https://manager.docs.scylladb.com/stable/sctool/index.html>`_ for suspending Scylla Manager (only available Scylla Enterprise) scheduled or running repairs.
|
||||
* Not to apply schema changes
|
||||
|
||||
.. note:: Before upgrading, make sure to use |SCYLLA_MONITOR|_ or newer, for the Dashboards.
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-src
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <rollback-procedure>` the upgrade. If you are not running a |SRC_VERSION|.x version, stop right here! This guide only covers |SRC_VERSION|.x to |NEW_VERSION|.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |SCYLLA_REPO|_ to |NEW_VERSION|
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
* More on |Scylla_METRICS|_
|
||||
|
||||
.. _rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from |SCYLLA_NAME| release |NEW_VERSION|.x to |SRC_VERSION|.y. Apply this procedure if an upgrade from |SRC_VERSION| to |NEW_VERSION| failed before completing on all nodes. Use this procedure only for nodes you upgraded to |NEW_VERSION|
|
||||
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to |SRC_VERSION|, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the |SCYLLA_REPO|_ to |SRC_VERSION|
|
||||
3. Install
|
||||
|
||||
.. parsed-literal::
|
||||
\ sudo yum clean all
|
||||
\ sudo rm -rf /var/cache/yum
|
||||
\ sudo yum remove scylla\\*tools-core
|
||||
\ sudo yum downgrade scylla\\* -y
|
||||
\ sudo yum install |PKG_NAME|
|
||||
\
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-src| /etc/scylla/scylla.yaml
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, |NEW_VERSION| uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,197 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - |SCYLLA_NAME| |SRC_VERSION| to |NEW_VERSION| for |OS|
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from |SCYLLA_NAME| |SRC_VERSION| to |SCYLLA_NAME| |NEW_VERSION|, and rollback to |SRC_VERSION| if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: |SRC_VERSION|.x or later to |SCYLLA_NAME| version |NEW_VERSION|.y on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 |NEW_VERSION| features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes. See `sctool <https://manager.docs.scylladb.com/stable/sctool/index.html>`_ for suspending Scylla Manager (only available Scylla Enterprise) scheduled or running repairs.
|
||||
* Not to apply schema changes
|
||||
|
||||
.. note:: Before upgrading, make sure to use |SCYLLA_MONITOR|_ or newer, for the Dashboards.
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-|SRC_VERSION|
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a |SRC_VERSION|.x version, stop right here! This guide only covers |SRC_VERSION|.x to |NEW_VERSION|.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |SCYLLA_REPO|_ to |NEW_VERSION|, and enable scylla/ppa repo
|
||||
|
||||
.. code:: sh
|
||||
|
||||
Ubuntu 16:
|
||||
sudo add-apt-repository -y ppa:scylladb/ppa
|
||||
|
||||
2. Config java to 1.8, which is requested by |SCYLLA_NAME| |NEW_VERSION|
|
||||
|
||||
* sudo apt-get update
|
||||
* sudo apt-get install -y |OPENJDK|
|
||||
* sudo update-java-alternatives -s java-1.8.0-openjdk-amd64
|
||||
|
||||
3. Install
|
||||
|
||||
.. parsed-literal::
|
||||
\ sudo apt-get update
|
||||
\ sudo apt-get dist-upgrade |PKG_NAME|
|
||||
\
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (by ``journalctl _COMM=scylla``) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
* More on |Scylla_METRICS|_
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from |SCYLLA_NAME| release |NEW_VERSION|.x to |SRC_VERSION|.y. Apply this procedure if an upgrade from |SRC_VERSION| to |NEW_VERSION| failed before completing on all nodes. Use this procedure only for nodes you upgraded to |NEW_VERSION|
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to |SRC_VERSION|, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the |SCYLLA_REPO|_ to |SRC_VERSION|
|
||||
3. install
|
||||
|
||||
.. parsed-literal::
|
||||
\ sudo apt-get update
|
||||
\ sudo apt-get remove scylla\* -y
|
||||
\ sudo apt-get install |PKG_NAME|
|
||||
\
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-|SRC_VERSION| /etc/scylla/scylla.yaml
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, |NEW_VERSION| uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,196 +0,0 @@
|
||||
=============================================================================================================
|
||||
Upgrade Guide - |SCYLLA_NAME| |SRC_VERSION| to |NEW_VERSION| for Red Hat Enterprise Linux 7 or CentOS 7
|
||||
=============================================================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from |SCYLLA_NAME| |SRC_VERSION| to |SCYLLA_NAME| |NEW_VERSION|, and rollback to |SRC_VERSION| if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: |SRC_VERSION|.x or later to |SCYLLA_NAME| version |NEW_VERSION|.y, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 |NEW_VERSION| features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes. See `sctool <https://manager.docs.scylladb.com/stable/sctool/index.html>`_ for suspending Scylla Manager (only available Scylla Enterprise) scheduled or running repairs.
|
||||
* Not to apply schema changes
|
||||
|
||||
.. note:: Before upgrading, make sure to use |SCYLLA_MONITOR|_ or newer, for the Dashboards.
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-src
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <rollback-procedure>` the upgrade. If you are not running a |SRC_VERSION|.x version, stop right here! This guide only covers |SRC_VERSION|.x to |NEW_VERSION|.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |SCYLLA_REPO|_ to |NEW_VERSION|
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
.. note::
|
||||
|
||||
Alternator users upgrading from Scylla 4.0 to 4.1, need to set :doc:`default isolation level </upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/alternator>`
|
||||
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
* More on |Scylla_METRICS|_
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from |SCYLLA_NAME| release |NEW_VERSION|.x to |SRC_VERSION|.y. Apply this procedure if an upgrade from |SRC_VERSION| to |NEW_VERSION| failed before completing on all nodes. Use this procedure only for nodes you upgraded to |NEW_VERSION|
|
||||
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to |SRC_VERSION|, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* Restore the configuration file
|
||||
* Reload systemd configuration
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the |SCYLLA_REPO|_ to |SRC_VERSION|
|
||||
3. Install
|
||||
|
||||
.. parsed-literal::
|
||||
\ sudo yum clean all
|
||||
\ sudo rm -rf /var/cache/yum
|
||||
\ sudo yum remove scylla\\*tools-core
|
||||
\ sudo yum downgrade scylla\\* -y
|
||||
\ sudo yum install |PKG_NAME|
|
||||
\
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-src| /etc/scylla/scylla.yaml
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, |NEW_VERSION| uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Reload systemd configuration
|
||||
---------------------------------
|
||||
|
||||
Require to reload the unit file if the systemd unit file is changed.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl daemon-reload
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,213 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - |SCYLLA_NAME| |SRC_VERSION| to |NEW_VERSION| for |OS|
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from |SCYLLA_NAME| |SRC_VERSION| to |SCYLLA_NAME| |NEW_VERSION|, and rollback to |SRC_VERSION| if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: |SRC_VERSION|.x or later to |SCYLLA_NAME| version |NEW_VERSION|.y on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 |NEW_VERSION| features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes. See `sctool <https://manager.docs.scylladb.com/stable/sctool/index.html>`_ for suspending Scylla Manager (only available Scylla Enterprise) scheduled or running repairs.
|
||||
* Not to apply schema changes
|
||||
|
||||
.. note:: Before upgrading, make sure to use |SCYLLA_MONITOR|_ or newer, for the Dashboards.
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-|SRC_VERSION|
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a |SRC_VERSION|.x version, stop right here! This guide only covers |SRC_VERSION|.x to |NEW_VERSION|.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |SCYLLA_REPO|_ to |NEW_VERSION|, and enable scylla/ppa repo
|
||||
|
||||
.. code:: sh
|
||||
|
||||
Ubuntu 16:
|
||||
sudo add-apt-repository -y ppa:scylladb/ppa
|
||||
|
||||
2. Config java to 1.8, which is requested by |SCYLLA_NAME| |NEW_VERSION|
|
||||
|
||||
* sudo apt-get update
|
||||
* sudo apt-get install -y |OPENJDK|
|
||||
* sudo update-java-alternatives -s java-1.8.0-openjdk-amd64
|
||||
|
||||
3. Install
|
||||
|
||||
.. parsed-literal::
|
||||
\ sudo apt-get update
|
||||
\ sudo apt-get dist-upgrade |PKG_NAME|
|
||||
\
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
|
||||
.. note::
|
||||
|
||||
Alternator users upgrading from Scylla 4.0 to 4.1, need to set :doc:`default isolation level </upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/alternator>`
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (by ``journalctl _COMM=scylla``) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
* More on |Scylla_METRICS|_
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from |SCYLLA_NAME| release |NEW_VERSION|.x to |SRC_VERSION|.y. Apply this procedure if an upgrade from |SRC_VERSION| to |NEW_VERSION| failed before completing on all nodes. Use this procedure only for nodes you upgraded to |NEW_VERSION|
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to |SRC_VERSION|, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* Restore the configuration file
|
||||
* Restore system tables
|
||||
* Reload systemd configuration
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the |SCYLLA_REPO|_ to |SRC_VERSION|
|
||||
3. install
|
||||
|
||||
.. parsed-literal::
|
||||
\ sudo apt-get update
|
||||
\ sudo apt-get remove scylla\* -y
|
||||
\ sudo apt-get install |PKG_NAME|
|
||||
\
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-|SRC_VERSION| /etc/scylla/scylla.yaml
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, |NEW_VERSION| uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Reload systemd configuration
|
||||
----------------------------
|
||||
|
||||
Require to reload the unit file if the systemd unit file is changed.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl daemon-reload
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,192 +0,0 @@
|
||||
=============================================================================================================
|
||||
Upgrade Guide - |SCYLLA_NAME| |SRC_VERSION| to |NEW_VERSION| for |OS|
|
||||
=============================================================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from |SCYLLA_NAME| |SRC_VERSION| to |SCYLLA_NAME| |NEW_VERSION|, and rollback to |SRC_VERSION| if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: |SRC_VERSION|.x or later to |SCYLLA_NAME| version |NEW_VERSION|.y, on the following platforms:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
Upgrading your Scylla 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 the Scylla service
|
||||
* Download and install new Scylla packages
|
||||
* Start the Scylla service
|
||||
* 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 |NEW_VERSION| features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes. See `sctool <https://manager.docs.scylladb.com/stable/sctool/index.html>`_ for suspending Scylla Manager (only available Scylla Enterprise) scheduled or running repairs.
|
||||
* Not to apply schema changes
|
||||
|
||||
.. note:: Before upgrading, make sure to use |SCYLLA_MONITOR|_ or newer, for the Dashboards.
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check the cluster schema
|
||||
------------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade as any schema disagreement between the nodes causes the upgrade to fail.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
Before any major procedure, like an upgrade, it is **highly 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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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 an external backup device.
|
||||
|
||||
When the upgrade is complete (for all nodes), remove the snapshot by running ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of disk space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-src
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. include:: /rst_include/scylla-commands-stop-index.rst
|
||||
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what Scylla version you are currently running with ``rpm -qa | grep scylla-server``. You should use the same version as this version in case you want to :ref:`rollback <rollback-procedure>` the upgrade. If you are not running a |SRC_VERSION|.x version, stop right here! This guide only covers |SRC_VERSION|.x to |NEW_VERSION|.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |SCYLLA_REPO|_ to |NEW_VERSION|
|
||||
2. Install the new Scylla version
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
.. note::
|
||||
|
||||
Alternator users upgrading from Scylla 4.0 to 4.1, need to set :doc:`default isolation level </upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/alternator>`
|
||||
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. include:: /rst_include/scylla-commands-start-index.rst
|
||||
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check the Scylla version. Validate that the version matches the one you upgraded to.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
* More on |Scylla_METRICS|_
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from |SCYLLA_NAME| release |NEW_VERSION|.x to |SRC_VERSION|.y. Apply this procedure if an upgrade from |SRC_VERSION| to |NEW_VERSION| failed before completing on all nodes. Use this procedure only for the nodes that you upgraded to |NEW_VERSION|
|
||||
|
||||
|
||||
Scylla rollback is a rolling procedure that does **not** require a full cluster shutdown.
|
||||
For each of the nodes rollback to |SRC_VERSION|, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* Restore the configuration file
|
||||
* Reload the systemd configuration
|
||||
* Restart the Scylla service
|
||||
* 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 with the old version.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
.. include:: /rst_include/scylla-commands-stop-index.rst
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the |SCYLLA_REPO|_ to |SRC_VERSION|
|
||||
3. Install
|
||||
|
||||
.. parsed-literal::
|
||||
\ sudo yum clean all
|
||||
\ sudo rm -rf /var/cache/yum
|
||||
\ sudo yum remove scylla\\*tools-core
|
||||
\ sudo yum downgrade scylla\\* -y
|
||||
\ sudo yum install |PKG_NAME|
|
||||
\
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-src| /etc/scylla/scylla.yaml
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, |NEW_VERSION| uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Reload systemd configuration
|
||||
---------------------------------
|
||||
|
||||
Require to reload the unit file if the systemd unit file is changed.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl daemon-reload
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
|
||||
.. include:: /rst_include/scylla-commands-start-index.rst
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check the upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster. Keep in mind that the version you want to see on your node is the old version, which you noted at the beginning of the procedure.
|
||||
@@ -1,203 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - |SCYLLA_NAME| |SRC_VERSION| to |NEW_VERSION| for |OS|
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from |SCYLLA_NAME| |SRC_VERSION| to |SCYLLA_NAME| |NEW_VERSION|, and rollback to |SRC_VERSION| if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: |SRC_VERSION|.x or later to |SCYLLA_NAME| version |NEW_VERSION|.y on the following platform:
|
||||
|
||||
* |OS|
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 |NEW_VERSION| features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes. See `sctool <https://manager.docs.scylladb.com/stable/sctool/index.html>`_ for suspending Scylla Manager (only available Scylla Enterprise) scheduled or running repairs.
|
||||
* Not to apply schema changes
|
||||
|
||||
.. note:: Before upgrading, make sure to use |SCYLLA_MONITOR|_ or newer, for the Dashboards.
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-|SRC_VERSION|
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to |ROLLBACK|_ the upgrade. If you are not running a |SRC_VERSION|.x version, stop right here! This guide only covers |SRC_VERSION|.x to |NEW_VERSION|.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the |SCYLLA_REPO|_ to |NEW_VERSION|
|
||||
|
||||
2. Install
|
||||
|
||||
.. parsed-literal::
|
||||
\ sudo apt-get clean all
|
||||
\ sudo apt-get update
|
||||
\ sudo apt-get dist-upgrade |PKG_NAME|
|
||||
\
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
|
||||
.. note::
|
||||
|
||||
Alternator users upgrading from Scylla 4.0 to 4.1, need to set :doc:`default isolation level </upgrade/upgrade-opensource/upgrade-guide-from-4.0-to-4.1/alternator>`
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (by ``journalctl _COMM=scylla``) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
* More on |Scylla_METRICS|_
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from |SCYLLA_NAME| release |NEW_VERSION|.x to |SRC_VERSION|.y. Apply this procedure if an upgrade from |SRC_VERSION| to |NEW_VERSION| failed before completing on all nodes. Use this procedure only for nodes you upgraded to |NEW_VERSION|
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to |SRC_VERSION|, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* Restore the configuration file
|
||||
* Restore system tables
|
||||
* Reload systemd configuration
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the |SCYLLA_REPO|_ to |SRC_VERSION|
|
||||
3. install
|
||||
|
||||
.. parsed-literal::
|
||||
\ sudo apt-get update
|
||||
\ sudo apt-get remove scylla\* -y
|
||||
\ sudo apt-get install |PKG_NAME|
|
||||
\
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-|SRC_VERSION| /etc/scylla/scylla.yaml
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, |NEW_VERSION| uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Reload systemd configuration
|
||||
----------------------------
|
||||
|
||||
Require to reload the unit file if the systemd unit file is changed.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl daemon-reload
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -69,7 +69,7 @@ Stop ScyllaDB
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <rollback-procedure>` the upgrade. If you are not running a |SRC_VERSION|.x version, stop right here! This guide only covers |SRC_VERSION|.x to |NEW_VERSION|.y upgrades.
|
||||
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 :ref:`rollback <rollback-procedure-v4>` the upgrade. If you are not running a |SRC_VERSION|.x version, stop right here! This guide only covers |SRC_VERSION|.x to |NEW_VERSION|.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
@@ -98,6 +98,8 @@ Once you are sure the node upgrade was successful, move to the next node in the
|
||||
|
||||
See |Scylla_METRICS|_ for more information..
|
||||
|
||||
.. _rollback-procedure-v4:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@ The following example shows the upgrade path for a 3-node cluster from version 4
|
||||
#. Upgrade all three nodes to version 4.6.
|
||||
|
||||
|
||||
Upgrading to each patch version by following the :doc:`Scylla Maintenance Release Upgrade Guide </upgrade/upgrade-opensource/upgrade-guide-from-4.x.y-to-4.x.z/index>`
|
||||
Upgrading to each patch version by following the Maintenance Release Upgrade Guide
|
||||
is optional. However, we recommend upgrading to the latest patch release for your version before upgrading to a new version.
|
||||
For example, upgrade to patch 4.4.8 before upgrading to version 4.5.
|
||||
|
||||
|
||||
@@ -10,25 +10,7 @@ Upgrade ScyllaDB Open Source
|
||||
ScyllaDB 5.0 to 5.1 <upgrade-guide-from-5.0-to-5.1/index>
|
||||
ScyllaDB 5.x maintenance release <upgrade-guide-from-5.x.y-to-5.x.z/index>
|
||||
ScyllaDB 4.6 to 5.0 <upgrade-guide-from-4.6-to-5.0/index>
|
||||
ScyllaDb 4.5 to 4.6 <upgrade-guide-from-4.5-to-4.6/index>
|
||||
ScyllaDB 4.4 to 4.5 <upgrade-guide-from-4.4-to-4.5/index>
|
||||
ScyllaDB 4.3 to 4.4 <upgrade-guide-from-4.3-to-4.4/index>
|
||||
ScyllaDB 4.2 to 4.3 <upgrade-guide-from-4.2-to-4.3/index>
|
||||
ScyllaDB 4.1 to 4.2 <upgrade-guide-from-4.1-to-4.2/index>
|
||||
ScyllaDB 4.x maintenance release <upgrade-guide-from-4.x.y-to-4.x.z/index>
|
||||
ScyllaDB 4.0 to 4.1 <upgrade-guide-from-4.0-to-4.1/index>
|
||||
ScyllaDB 3.x maintenance release <upgrade-guide-from-3.x.y-to-3.x.z/index>
|
||||
ScyllaDB 3.3 to 4.0 <upgrade-guide-from-3.3-to-4.0/index>
|
||||
ScyllaDB 3.2 to 3.3 <upgrade-guide-from-3.2-to-3.3/index>
|
||||
ScyllaDB 3.1 to 3.2 <upgrade-guide-from-3.1-to-3.2/index>
|
||||
ScyllaDB 3.0 to 3.1 <upgrade-guide-from-3.0-to-3.1/index>
|
||||
ScyllaDB 2.3 to 3.0 <upgrade-guide-from-2.3-to-3.0/index>
|
||||
ScyllaDB 2.2 to 2.3 <upgrade-guide-from-2.2-to-2.3/index>
|
||||
ScyllaDB 2.1 to 2.2 <upgrade-guide-from-2.1-to-2.2/index>
|
||||
ScyllaDB 2.x maintenance release <upgrade-guide-from-2.x.y-to-2.x.z/index>
|
||||
Older versions <upgrade-archive>
|
||||
Ubuntu 14.04 to 16.04 <upgrade-guide-from-ubuntu-14-to-16>
|
||||
|
||||
|
||||
|
||||
.. panel-box::
|
||||
:title: Upgrade ScyllaDB Open Source
|
||||
@@ -43,22 +25,4 @@ Upgrade ScyllaDB Open Source
|
||||
* :doc:`Upgrade Guide - ScyllaDB 5.0 to 5.1 <upgrade-guide-from-5.0-to-5.1/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 5.x maintenance releases <upgrade-guide-from-5.x.y-to-5.x.z/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 4.6 to 5.0 <upgrade-guide-from-4.6-to-5.0/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 4.5 to 4.6 <upgrade-guide-from-4.5-to-4.6/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 4.4 to 4.5 <upgrade-guide-from-4.4-to-4.5/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 4.3 to 4.4 <upgrade-guide-from-4.3-to-4.4/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 4.2 to 4.3 <upgrade-guide-from-4.2-to-4.3/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 4.1 to 4.2 <upgrade-guide-from-4.1-to-4.2/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 4.x maintenance release <upgrade-guide-from-4.x.y-to-4.x.z/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 4.0 to 4.1 <upgrade-guide-from-4.0-to-4.1/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 3.x maintenance release <upgrade-guide-from-3.x.y-to-3.x.z/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 3.3 to 4.0 <upgrade-guide-from-3.3-to-4.0/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 3.2 to 3.3 <upgrade-guide-from-3.2-to-3.3/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 3.1 to 3.2 <upgrade-guide-from-3.1-to-3.2/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 3.0 to 3.1 <upgrade-guide-from-3.0-to-3.1/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 2.3 to 3.0 <upgrade-guide-from-2.3-to-3.0/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 2.2 to 2.3 <upgrade-guide-from-2.2-to-2.3/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 2.1 to 2.2 <upgrade-guide-from-2.1-to-2.2/index>`
|
||||
* :doc:`Upgrade Guide - ScyllaDB 2.x maintenance release <upgrade-guide-from-2.x.y-to-2.x.z/index>`
|
||||
* :doc:`Upgrade Guide - older versions <upgrade-archive>`
|
||||
* :doc:`Upgrade Guide - Ubuntu 14.04 to 16.04 <upgrade-guide-from-ubuntu-14-to-16>`
|
||||
* :ref:`Upgrade Unified Installer (relocatable executable) install <unified-installed-upgrade>`
|
||||
|
||||
@@ -1,59 +0,0 @@
|
||||
==========================================
|
||||
Upgrade Scylla Opensource - older versions
|
||||
==========================================
|
||||
|
||||
.. toctree::
|
||||
:hidden:
|
||||
|
||||
Scylla 2.0 to 2.1 <upgrade-guide-from-2.0-to-2.1/index>
|
||||
Scylla 1.7 to 2.0 <upgrade-guide-from-1.7-to-2.0/index>
|
||||
Scylla 1.6 to 1.7 <upgrade-guide-from-1.6-to-1.7/index>
|
||||
Scylla 1.5 to 1.6 <upgrade-guide-from-1.5-to-1.6/index>
|
||||
Scylla 1.4 to 1.5 <upgrade-guide-from-1.4-to-1.5/index>
|
||||
Scylla 1.3 to 1.4 <upgrade-guide-from-1.3-to-1.4/index>
|
||||
Scylla 1.2 to 1.3 <upgrade-guide-from-1.2-to-1.3/index>
|
||||
Scylla 1.1 to 1.2 <upgrade-guide-from-1.1-to-1.2/index>
|
||||
Scylla 1.0 to 1.1 <upgrade-guide-from-1.0-to-1.1/index>
|
||||
Scylla 1.x maintenance release <upgrade-guide-from-1.x.y-to-1.x.z/index>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla Open Source</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
Procedures for upgrading to a newer version of Scylla Open Source. For the latest open source versions see :doc:`here </upgrade/upgrade-opensource/index>`.
|
||||
|
||||
* :doc:`Upgrade Guide - Scylla 2.0 to 2.1 </upgrade/upgrade-opensource/upgrade-guide-from-2.0-to-2.1/index>`
|
||||
|
||||
* :doc:`Upgrade Guide - Scylla 1.x maintenance release </upgrade/upgrade-opensource/upgrade-guide-from-1.x.y-to-1.x.z/index>`
|
||||
|
||||
* :doc:`Upgrade Guide - Scylla 1.7 to 2.0 </upgrade/upgrade-opensource/upgrade-guide-from-1.7-to-2.0/index>`
|
||||
|
||||
* :doc:`Upgrade Guide - Scylla 1.6 to 1.7 </upgrade/upgrade-opensource/upgrade-guide-from-1.6-to-1.7/index>`
|
||||
|
||||
* :doc:`Upgrade Guide - Scylla 1.5 to 1.6 </upgrade/upgrade-opensource/upgrade-guide-from-1.5-to-1.6/index>`
|
||||
|
||||
* :doc:`Upgrade Guide - Scylla 1.4 to 1.5 </upgrade/upgrade-opensource/upgrade-guide-from-1.4-to-1.5/index>`
|
||||
|
||||
* :doc:`Upgrade Guide - Scylla 1.3 to 1.4 </upgrade/upgrade-opensource/upgrade-guide-from-1.3-to-1.4/index>`
|
||||
|
||||
* :doc:`Upgrade Guide - Scylla 1.2 to 1.3 </upgrade/upgrade-opensource/upgrade-guide-from-1.2-to-1.3/index>`
|
||||
|
||||
* :doc:`Upgrade Guide - Scylla 1.1 to 1.2 </upgrade/upgrade-opensource/upgrade-guide-from-1.1-to-1.2/index>`
|
||||
|
||||
* :doc:`Upgrade Guide - Scylla 1.0 to 1.1 </upgrade/upgrade-opensource/upgrade-guide-from-1.0-to-1.1/index>`
|
||||
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
@@ -1,16 +0,0 @@
|
||||
=================================
|
||||
Upgrade - Scylla 1.0 to 1.1
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Fedora, Red Hat Enterprise Linux, and CentOS <upgrade-guide-from-1.0-to-1.1-rpm>
|
||||
Ubuntu <upgrade-guide-from-1.0-to-1.1-ubuntu>
|
||||
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 1.0.x to 1.1.y on Fedora, Red Hat Enterprise Linux, and CentOS <upgrade-guide-from-1.0-to-1.1-rpm>`
|
||||
* :doc:`Upgrade Scylla from 1.0.x to 1.1.y on Ubuntu <upgrade-guide-from-1.0-to-1.1-ubuntu>`
|
||||
@@ -1,183 +0,0 @@
|
||||
==================================================================
|
||||
Upgrade Guide - Scylla 1.0 to 1.1 for Red Hat Enterprise or CentOS
|
||||
==================================================================
|
||||
This document is a step by step procedure for upgrading from Scylla 1.0
|
||||
to Scylla 1.1, and rollback to 1.0 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
-------------------
|
||||
|
||||
This guide covers upgrading Scylla from the following versions: 1.0.x to
|
||||
Scylla version 1.1.y, on the following platforms:
|
||||
|
||||
- Fedora 22
|
||||
|
||||
- Red Hat Enterprise Linux, version 7 and later
|
||||
|
||||
- CentOS, version 7 and later
|
||||
|
||||
Upgrade Procedure
|
||||
-----------------
|
||||
|
||||
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.1 features
|
||||
- Not to run administration functions, like repairs, refresh, rebuild
|
||||
or add or remove nodes
|
||||
- Not to apply schema changes
|
||||
|
||||
Backup the data
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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.
|
||||
|
||||
Upgrade steps
|
||||
-------------
|
||||
|
||||
Backup configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.0
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
Download and install the new release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
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
|
||||
:ref:`rollback <upgrade-1.0-1.1-rpm-rollback-procedure>` the
|
||||
upgrade. If you are not running a 1.0.x version, stop right here! This
|
||||
guide only covers 1.0.x to 1.1.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/#fndtn-RPM>`_ to
|
||||
**1.1**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum update scylla-server scylla-jmx scylla-tools -y
|
||||
|
||||
Gracefully restart the node
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl restart scylla-server.service
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all**
|
||||
nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``journalctl _COMM=scylla`` to check there are no new errors in
|
||||
the log.
|
||||
3. 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.
|
||||
|
||||
.. _upgrade-1.0-1.1-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
------------------
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.1.x
|
||||
to 1.0.y. Apply this procedure if an upgrade from 1.0 to 1.1 failed
|
||||
before completing on all nodes. Use this procedure only for nodes you
|
||||
upgraded to 1.1
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full
|
||||
cluster shutdown. For each of the nodes rollback to 1.0, 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.
|
||||
|
||||
Rollback steps
|
||||
--------------
|
||||
|
||||
Download and install the new release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/#fndtn-RPM>`_ to
|
||||
**1.0**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum downgrade scylla-server scylla-jmx scylla-tools -y
|
||||
|
||||
Gracefully shutdown Scylla
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
Restore the configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.0 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server.service
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
Check upgrade instruction above for validation. Once you are sure the
|
||||
node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,185 +0,0 @@
|
||||
============================================
|
||||
Upgrade Guide - Scylla 1.0 to 1.1 for Ubuntu
|
||||
============================================
|
||||
This document is a step by step procedure for upgrading from Scylla 1.0
|
||||
to Scylla 1.1, and rollback to 1.0 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
-------------------
|
||||
|
||||
This guide covers upgrading Scylla from the following versions: 1.0.x to
|
||||
Scylla version 1.1.y on the following platform:
|
||||
|
||||
- Ubuntu 14.04
|
||||
|
||||
Upgrade Procedure
|
||||
-----------------
|
||||
|
||||
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.1 features
|
||||
- Not to run administration functions, like repairs, refresh, rebuild
|
||||
or add or remove nodes
|
||||
- Not to apply schema changes
|
||||
|
||||
Backup the data
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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.
|
||||
|
||||
Upgrade steps
|
||||
-------------
|
||||
|
||||
Backup configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.0
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
Download and install the new release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Before upgrading, check what version you are running now using
|
||||
``dpkg -s scylla-server``. You should use the same version in case you
|
||||
want to :ref:`rollback <upgrade-1.0-1.1-ubuntu-rollback-procedure>`
|
||||
the upgrade. If you are not running a 1.0.x version, stop right here!
|
||||
This guide only covers 1.0.x to 1.1.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to
|
||||
**1.1**
|
||||
2. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get upgrade scylla-server scylla-jmx scylla-tools
|
||||
|
||||
Answer ‘y’ to the first two questions and 'n' when asked to overwrite
|
||||
``scylla.yaml``.
|
||||
|
||||
Gracefully restart the node
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server restart
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all**
|
||||
nodes, including the one you just upgraded, are in UN status.
|
||||
2. Check ``/var/log/upstart/scylla-server.log`` and ``/var/log/syslog``
|
||||
to validate there are no errors.
|
||||
3. 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.
|
||||
|
||||
.. _upgrade-1.0-1.1-ubuntu-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
------------------
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.1.x
|
||||
to 1.0.y. Apply this procedure if an upgrade from 1.0 to 1.1 failed
|
||||
before completing on all nodes. Use this procedure only for nodes you
|
||||
upgraded to 1.1
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full
|
||||
cluster shutdown. For each of the nodes rollback to 1.0, 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.
|
||||
|
||||
Rollback steps
|
||||
--------------
|
||||
|
||||
download and install the old release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to
|
||||
**1.0**
|
||||
3. install
|
||||
|
||||
::
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove --assume-yes scylla-server scylla-jmx scylla-tools
|
||||
sudo apt-get install scylla-server scylla-jmx scylla-tools
|
||||
|
||||
Answer ‘y’ to the first two questions and 'n' when asked to overwrite
|
||||
``scylla.yaml``.
|
||||
|
||||
Gracefully shutdown Scylla
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server.service
|
||||
|
||||
Restore the configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.0 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
Check upgrade instruction above for validation. Once you are sure the
|
||||
node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,33 +0,0 @@
|
||||
=================================
|
||||
Upgrade - Scylla 1.1 to 1.2
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Fedora, Red Hat Enterprise Linux, and CentOS <upgrade-guide-from-1.1-to-1.2-rpm>
|
||||
Ubuntu <upgrade-guide-from-1.1-to-1.2-ubuntu>
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla from 1.1 to 1.2</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 1.1.x to 1.2.y on Fedora, Red Hat Enterprise Linux, and CentOS <upgrade-guide-from-1.1-to-1.2-rpm>`
|
||||
* :doc:`Upgrade Scylla from 1.1.x to 1.2.y on Ubuntu <upgrade-guide-from-1.1-to-1.2-ubuntu>`
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1,185 +0,0 @@
|
||||
==================================================================
|
||||
Upgrade Guide - Scylla 1.1 to 1.2 for Red Hat Enterprise or CentOS
|
||||
==================================================================
|
||||
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.
|
||||
|
||||
|
||||
Applicable versions
|
||||
-------------------
|
||||
|
||||
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
|
||||
|
||||
Upgrade Procedure
|
||||
-----------------
|
||||
|
||||
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
|
||||
|
||||
Backup the data
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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.
|
||||
|
||||
Upgrade steps
|
||||
-------------
|
||||
|
||||
Backup configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.1
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
Download and install the new release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
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
|
||||
:ref:`rollback <upgrade-1.1-1.2-rpm-rollback-procedure>` 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:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/#fndtn-RPM>`_ to
|
||||
**1.2**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum update scylla-server scylla-jmx scylla-tools -y
|
||||
sudo yum install scylla
|
||||
|
||||
Gracefully restart the node
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl restart scylla-server.service
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all**
|
||||
nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``journalctl _COMM=scylla`` to check there are no new errors in
|
||||
the log.
|
||||
3. 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.
|
||||
|
||||
.. _upgrade-1.1-1.2-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
------------------
|
||||
|
||||
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.
|
||||
|
||||
Rollback steps
|
||||
--------------
|
||||
|
||||
Download and install the new release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/#fndtn-RPM>`_ to
|
||||
**1.1**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum remove scylla
|
||||
sudo yum downgrade scylla-server scylla-jmx scylla-tools -y
|
||||
|
||||
Gracefully shutdown Scylla
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
Restore the configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.1 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server.service
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
Check upgrade instruction above for validation. Once you are sure the
|
||||
node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,191 +0,0 @@
|
||||
============================================
|
||||
Upgrade Guide - Scylla 1.1 to 1.2 for Ubuntu
|
||||
============================================
|
||||
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.
|
||||
|
||||
|
||||
Applicable versions
|
||||
-------------------
|
||||
|
||||
This guide covers upgrading Scylla from the following versions: 1.1.x to
|
||||
Scylla version 1.2.y on the following platform:
|
||||
|
||||
- Ubuntu 14.04
|
||||
|
||||
Upgrade Procedure
|
||||
-----------------
|
||||
|
||||
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
|
||||
|
||||
Backup the data
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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.
|
||||
|
||||
Upgrade steps
|
||||
-------------
|
||||
|
||||
Backup configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.1
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
Download and install the new release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Before upgrading, check what version you are running now using
|
||||
``dpkg -s scylla-server``. You should use the same version in case you
|
||||
want to :ref:`rollback <upgrade-1.1-1.2-ubuntu-rollback-procedure>`
|
||||
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:
|
||||
|
||||
1. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to
|
||||
**1.2**
|
||||
2. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla-server scylla-jmx scylla-tools
|
||||
|
||||
Answer 'y'
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions and 'n' when asked to overwrite
|
||||
``scylla.yaml``.
|
||||
|
||||
Gracefully restart the node
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server restart
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all**
|
||||
nodes, including the one you just upgraded, are in UN status.
|
||||
2. Check ``/var/log/upstart/scylla-server.log`` and ``/var/log/syslog``
|
||||
to validate there are no errors.
|
||||
3. 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.
|
||||
|
||||
.. _upgrade-1.1-1.2-ubuntu-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
------------------
|
||||
|
||||
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.
|
||||
|
||||
Rollback steps
|
||||
--------------
|
||||
|
||||
download and install the old release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to
|
||||
**1.1**
|
||||
3. install
|
||||
|
||||
::
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove --assume-yes scylla-conf scylla-server scylla-jmx scylla-tools
|
||||
sudo apt-get install scylla-server scylla-jmx scylla-tools
|
||||
|
||||
Answer ‘y’ to the first question and 'n' when asked to overwrite
|
||||
``scylla.yaml``.
|
||||
|
||||
Gracefully shutdown Scylla
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
Restore the configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.1 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
Check upgrade instruction above for validation. Once you are sure the
|
||||
node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,32 +0,0 @@
|
||||
=================================
|
||||
Upgrade Guide - Scylla 1.2 to 1.3
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.2-to-1.3-rpm>
|
||||
Ubuntu <upgrade-guide-from-1.2-to-1.3-ubuntu>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla from 1.2 to 1.3</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 1.2.x to 1.3.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.2-to-1.3-rpm>`
|
||||
* :doc:`Upgrade Scylla from 1.2.x to 1.3.y on Ubuntu <upgrade-guide-from-1.2-to-1.3-ubuntu>`
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1,186 +0,0 @@
|
||||
==================================================================
|
||||
Upgrade Guide - Scylla 1.2 to 1.3 for Red Hat Enterprise or CentOS
|
||||
==================================================================
|
||||
This document is a step by step procedure for upgrading from Scylla 1.2
|
||||
to Scylla 1.3, and rollback to 1.2 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
-------------------
|
||||
|
||||
This guide covers upgrading Scylla from the following versions: 1.2.x to
|
||||
Scylla version 1.3.y, on the following platforms:
|
||||
|
||||
- Red Hat Enterprise Linux, version 7 and later
|
||||
|
||||
- CentOS, version 7 and later
|
||||
|
||||
- No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
-----------------
|
||||
|
||||
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.3 features
|
||||
- Not to run administration functions, like repairs, refresh, rebuild
|
||||
or add or remove nodes
|
||||
- Not to apply schema changes
|
||||
|
||||
Backup the data
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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.
|
||||
|
||||
Upgrade steps
|
||||
-------------
|
||||
|
||||
Backup configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.2
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
Download and install the new release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
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
|
||||
:ref:`rollback <upgrade-1.2-1.3-rpm-rollback-procedure>` the
|
||||
upgrade. If you are not running a 1.2.x version, stop right here! This
|
||||
guide only covers 1.2.x to 1.3.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/#fndtn-RPM>`_ to
|
||||
**1.3**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum update scylla scylla-server scylla-jmx scylla-tools scylla-conf scylla-kernel-conf -y
|
||||
|
||||
Gracefully restart the node
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server restart
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all**
|
||||
nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use
|
||||
``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"``
|
||||
to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in
|
||||
the log.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-1.2-1.3-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
------------------
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.3.x
|
||||
to 1.2.y. Apply this procedure if an upgrade from 1.2 to 1.3 failed
|
||||
before completing on all nodes. Use this procedure only for nodes you
|
||||
upgraded to 1.3
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full
|
||||
cluster shutdown. For each of the nodes rollback to 1.2, 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.
|
||||
|
||||
Rollback steps
|
||||
--------------
|
||||
|
||||
Download and install the new release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/#fndtn-RPM>`_ to
|
||||
**1.2**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum downgrade scylla scylla-server scylla-jmx scylla-tools scylla-conf scylla-kernel-conf -y
|
||||
|
||||
Gracefully shutdown Scylla
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
Restore the configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.2 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
Check upgrade instruction above for validation. Once you are sure the
|
||||
node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,187 +0,0 @@
|
||||
============================================
|
||||
Upgrade Guide - Scylla 1.2 to 1.3 for Ubuntu
|
||||
============================================
|
||||
This document is a step by step procedure for upgrading from Scylla 1.2
|
||||
to Scylla 1.3, and rollback to 1.2 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
-------------------
|
||||
|
||||
This guide covers upgrading Scylla from the following versions: 1.2.x to
|
||||
Scylla version 1.3.y on the following platform:
|
||||
|
||||
- Ubuntu 14.04
|
||||
- Ubuntu 16.04
|
||||
|
||||
Upgrade Procedure
|
||||
-----------------
|
||||
|
||||
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.3 features
|
||||
- Not to run administration functions, like repairs, refresh, rebuild
|
||||
or add or remove nodes
|
||||
- Not to apply schema changes
|
||||
|
||||
Backup the data
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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.
|
||||
|
||||
Upgrade steps
|
||||
-------------
|
||||
|
||||
Backup configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.2
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
Download and install the new release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Before upgrading, check what version you are running now using
|
||||
``dpkg -s scylla-server``. You should use the same version in case you
|
||||
want to :ref:`rollback <upgrade-1.2-1.3-ubuntu-rollback-procedure>`
|
||||
the upgrade. If you are not running a 1.2.x version, stop right here!
|
||||
This guide only covers 1.2.x to 1.3.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to
|
||||
**1.3**
|
||||
2. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Gracefully restart the node
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server restart
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all**
|
||||
nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use
|
||||
``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"``
|
||||
to check scylla version.
|
||||
3. Check ``/var/log/upstart/scylla-server.log`` and ``/var/log/syslog``
|
||||
to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-1.2-1.3-ubuntu-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
------------------
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.3.x
|
||||
to 1.2.y. Apply this procedure if an upgrade from 1.2 to 1.3 failed
|
||||
before completing on all nodes. Use this procedure only for nodes you
|
||||
upgraded to 1.3
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full
|
||||
cluster shutdown. For each of the nodes rollback to 1.2, 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.
|
||||
|
||||
Rollback steps
|
||||
--------------
|
||||
|
||||
download and install the old release
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to
|
||||
**1.2**
|
||||
3. install
|
||||
|
||||
::
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla scylla-server scylla-jmx scylla-tools scylla-conf scylla-kernel-conf -y
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Gracefully shutdown Scylla
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
Restore the configuration file
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.2 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
~~~~~~~~
|
||||
|
||||
Check upgrade instruction above for validation. Once you are sure the
|
||||
node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,34 +0,0 @@
|
||||
=================================
|
||||
Upgrade Guide - Scylla 1.3 to 1.4
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.3-to-1.4-rpm>
|
||||
Ubuntu <upgrade-guide-from-1.3-to-1.4-ubuntu>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla from 1.3 to 1.4</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 1.3.x to 1.4.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.3-to-1.4-rpm>`
|
||||
|
||||
* :doc:`Upgrade Scylla from 1.3.x to 1.4.y on Ubuntu <upgrade-guide-from-1.3-to-1.4-ubuntu>`
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1,202 +0,0 @@
|
||||
======================================================================
|
||||
Upgrade Guide - Scylla 1.3 to 1.4 for Red Hat Enterprise 7 or CentOS 7
|
||||
======================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.3
|
||||
to Scylla 1.4, and rollback to 1.3 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
|
||||
This guide covers upgrading Scylla from the following versions: 1.3.x to
|
||||
Scylla version 1.4.y, on the following platforms:
|
||||
|
||||
- Red Hat Enterprise Linux, version 7 and later
|
||||
|
||||
- CentOS, version 7 and later
|
||||
|
||||
- No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
- drain node and backup the data
|
||||
- check your current release
|
||||
- backup configuration file
|
||||
- stop Scylla
|
||||
- download and install new Scylla packages
|
||||
- start 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.4 features
|
||||
- Not to run administration functions, like repairs, refresh, rebuild
|
||||
or add or remove nodes
|
||||
- Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed
|
||||
by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of
|
||||
space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.3
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
|
||||
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
|
||||
:ref:`rollback <upgrade-1.3-1.4-rpm-rollback-procedure>` the
|
||||
upgrade. If you are not running a 1.3.x version, stop right here! This
|
||||
guide only covers 1.3.x to 1.4.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/centos_rpm>`_ to
|
||||
**1.4**
|
||||
2. install
|
||||
|
||||
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all**
|
||||
nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use
|
||||
``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"``
|
||||
to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in
|
||||
the log.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-1.3-1.4-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.4.x
|
||||
to 1.3.y. Apply this procedure if an upgrade from 1.3 to 1.4 failed
|
||||
before completing on all nodes. Use this procedure only for nodes you
|
||||
upgraded to 1.4
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full
|
||||
cluster shutdown. For each of the nodes rollback to 1.3, you will:
|
||||
|
||||
- drain the node and stop Scylla
|
||||
- retrieve the old Scylla packages
|
||||
- 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/centos_rpm>`_ to
|
||||
**1.3**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum downgrade scylla\* -y
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.3 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
|
||||
Check upgrade instruction above for validation. Once you are sure the
|
||||
node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,201 +0,0 @@
|
||||
===========================================================
|
||||
Upgrade Guide - Scylla 1.3 to 1.4 for Ubuntu 14.04 or 16.04
|
||||
===========================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.3
|
||||
to Scylla 1.4, and rollback to 1.3 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
|
||||
This guide covers upgrading Scylla from the following versions: 1.3.x to
|
||||
Scylla version 1.4.y on the following platform:
|
||||
|
||||
- Ubuntu 14.04
|
||||
- Ubuntu 16.04
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full
|
||||
cluster shutdown. For each of the nodes in the cluster, you will:
|
||||
|
||||
- drain node and backup the data
|
||||
- check your current release
|
||||
- backup configuration file
|
||||
- stop Scylla
|
||||
- download and install new Scylla packages
|
||||
- start 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.4 features
|
||||
- Not to run administration functions, like repairs, refresh, rebuild
|
||||
or add or remove nodes
|
||||
- Not to apply schema changes
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed
|
||||
by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of
|
||||
space.
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.3
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
|
||||
Before upgrading, check what version you are running now using
|
||||
``dpkg -s scylla-server``. You should use the same version in case you
|
||||
want to :ref:`rollback <upgrade-1.3-1.4-ubuntu-rollback-procedure>`
|
||||
the upgrade. If you are not running a 1.3.x version, stop right here!
|
||||
This guide only covers 1.3.x to 1.4.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to
|
||||
**1.4**
|
||||
2. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all**
|
||||
nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use
|
||||
``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"``
|
||||
to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log``
|
||||
for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu
|
||||
16.04) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-1.3-1.4-ubuntu-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.4.x
|
||||
to 1.3.y. Apply this procedure if an upgrade from 1.3 to 1.4 failed
|
||||
before completing on all nodes. Use this procedure only for nodes you
|
||||
upgraded to 1.4
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full
|
||||
cluster shutdown. For each of the nodes rollback to 1.3, you will:
|
||||
|
||||
- drain the node and stop Scylla
|
||||
- retrieve the old Scylla packages
|
||||
- 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to
|
||||
**1.3**
|
||||
3. install
|
||||
|
||||
::
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla\* -y
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.3 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
|
||||
Check upgrade instruction above for validation. Once you are sure the
|
||||
node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,32 +0,0 @@
|
||||
=================================
|
||||
Upgrade Guide - Scylla 1.4 to 1.5
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.4-to-1.5-rpm>
|
||||
Ubuntu <upgrade-guide-from-1.4-to-1.5-ubuntu>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla from 1.4 to 1.5</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 1.4.x to 1.5.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.4-to-1.5-rpm>`
|
||||
* :doc:`Upgrade Scylla from 1.4.x to 1.5.y on Ubuntu <upgrade-guide-from-1.4-to-1.5-ubuntu>`
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -1,157 +0,0 @@
|
||||
======================================================================
|
||||
Upgrade Guide - Scylla 1.4 to 1.5 for Red Hat Enterprise 7 or CentOS 7
|
||||
======================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.4 to Scylla 1.5, and rollback to 1.4 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 1.4.x to Scylla version 1.5.y, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
A Scylla upgrade is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes in the cluster, you will:
|
||||
|
||||
* drain node and backup the data
|
||||
* check your current release
|
||||
* backup configuration file
|
||||
* stop Scylla
|
||||
* download and install new Scylla packages
|
||||
* start 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.5 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.4
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <upgrade-1.4-1.5-rpm-rollback-procedure>` the upgrade. If you are not running a 1.4.x version, stop right here! This guide only covers 1.4.x to 1.5.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/centos_rpm>`_ to **1.5**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-1.4-1.5-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.5.x to 1.4.y. Apply this procedure if an upgrade from 1.4 to 1.5 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 1.5
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 1.4, you will:
|
||||
|
||||
* drain the node and stop Scylla
|
||||
* retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/centos_rpm>`_ to **1.4**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum downgrade scylla\* -y
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.4 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,160 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 1.4 to 1.5 for Ubuntu 14.04 or 16.04
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.4 to Scylla 1.5, and rollback to 1.4 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 1.4.x to Scylla version 1.5.y on the following platform:
|
||||
|
||||
* Ubuntu 14.04
|
||||
* Ubuntu 16.04
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
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:
|
||||
|
||||
* drain node and backup the data
|
||||
* check your current release
|
||||
* backup configuration file
|
||||
* stop Scylla
|
||||
* download and install new Scylla packages
|
||||
* start 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.5 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.4
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to :ref:`rollback <upgrade-1.4-1.5-ubuntu-rollback-procedure>` the upgrade. If you are not running a 1.4.x version, stop right here! This guide only covers 1.4.x to 1.5.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to **1.5**
|
||||
2. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-1.4-1.5-ubuntu-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
The following procedure describes a rollback from Scylla release 1.5.x to 1.4.y. Apply this procedure if an upgrade from 1.4 to 1.5 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 1.5
|
||||
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 1.4, you will:
|
||||
|
||||
* drain the node and stop Scylla
|
||||
* retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to **1.4**
|
||||
3. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla\* -y
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.4 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,30 +0,0 @@
|
||||
=================================
|
||||
Upgrade Guide - Scylla 1.5 to 1.6
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.5-to-1.6-rpm>
|
||||
Ubuntu <upgrade-guide-from-1.5-to-1.6-ubuntu>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla from 1.5 to 1.6</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 1.5.x to 1.6.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.5-to-1.6-rpm>`
|
||||
* :doc:`Upgrade Scylla from 1.5.x to 1.6.y on Ubuntu <upgrade-guide-from-1.5-to-1.6-ubuntu>`
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1,156 +0,0 @@
|
||||
======================================================================
|
||||
Upgrade Guide - Scylla 1.5 to 1.6 for Red Hat Enterprise 7 or CentOS 7
|
||||
======================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.5 to Scylla 1.6, and rollback to 1.5 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 1.5.x to Scylla version 1.6.y, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* drain node and backup the data
|
||||
* check your current release
|
||||
* backup configuration file
|
||||
* stop Scylla
|
||||
* download and install new Scylla packages
|
||||
* start 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.6 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.5
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <upgrade-1.5-1.6-rpm-rollback-procedure>` the upgrade. If you are not running a 1.5.x version, stop right here! This guide only covers 1.5.x to 1.6.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/centos_rpm>`_ to **1.6**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-1.5-1.6-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.6.x to 1.5.y. Apply this procedure if an upgrade from 1.5 to 1.6 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 1.6
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 1.5, you will:
|
||||
|
||||
* drain the node and stop Scylla
|
||||
* retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/centos_rpm>`_ to **1.5**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum downgrade scylla\* -y
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.5 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,160 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 1.5 to 1.6 for Ubuntu 14.04 or 16.04
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.5 to Scylla 1.6, and rollback to 1.5 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 1.5.x to Scylla version 1.6.y on the following platform:
|
||||
|
||||
* Ubuntu 14.04
|
||||
* Ubuntu 16.04
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
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:
|
||||
|
||||
* drain node and backup the data
|
||||
* check your current release
|
||||
* backup configuration file
|
||||
* stop Scylla
|
||||
* download and install new Scylla packages
|
||||
* start 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.6 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.5
|
||||
|
||||
Gracefully stop the node
|
||||
------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server stop
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
Before upgrading, check what version you are running now using ``dpkg -s scylla-server``. You should use the same version in case you want to :ref:`rollback <upgrade-1.5-1.6-ubuntu-rollback-procedure>` the upgrade. If you are not running a 1.5.x version, stop right here! This guide only covers 1.5.x to 1.6.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to **1.6**
|
||||
2. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get dist-upgrade scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Check scylla-server log (check ``/var/log/upstart/scylla-server.log`` for Ubuntu 14.04, execute ``journalctl _COMM=scylla`` for Ubuntu 16.04) and ``/var/log/syslog`` to validate there are no errors.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-1.5-1.6-ubuntu-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
The following procedure describes a rollback from Scylla release 1.6.x to 1.5.y. Apply this procedure if an upgrade from 1.5 to 1.6 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 1.6
|
||||
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 1.5, you will:
|
||||
|
||||
* drain the node and stop Scylla
|
||||
* retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo service scylla-server stop
|
||||
|
||||
download and install the old release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/apt/sources.list.d/scylla.list
|
||||
|
||||
2. Update the `Scylla deb repo <http://www.scylladb.com/download/#fndtn-deb>`_ to **1.5**
|
||||
3. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get remove scylla\* -y
|
||||
sudo apt-get install scylla
|
||||
|
||||
Answer ‘y’ to the first two questions.
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.5 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo service scylla-server start
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,37 +0,0 @@
|
||||
=================================
|
||||
Upgrade Guide - Scylla 1.6 to 1.7
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.6-to-1.7-rpm>
|
||||
Ubuntu <upgrade-guide-from-1.6-to-1.7-ubuntu>
|
||||
Debian <upgrade-guide-from-1.6-to-1.7-debian>
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla from 1.6 to 1.7</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 1.6.x to 1.7.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.6-to-1.7-rpm>`
|
||||
* :doc:`Upgrade Scylla from 1.6.x to 1.7.y on Ubuntu <upgrade-guide-from-1.6-to-1.7-ubuntu>`
|
||||
* :doc:`Upgrade Scylla from 1.6.x to 1.7.y on Debian <upgrade-guide-from-1.6-to-1.7-debian>`
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Debian 8
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-1.6-to-1.7/upgrade-guide-from-1.6-to-1.7-debian/#upgrade-1-6-1-7-rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/#fndtn-Debian
|
||||
.. |ENABLE_APT_REPO| replace:: echo 'deb http://http.debian.net/debian jessie-backports main' > /etc/apt/sources.list.d/jessie-backports.list
|
||||
.. |JESSIE_BACKPORTS| replace:: -t jessie-backports openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-1.6-to-1.7-ubuntu-and-debian.rst
|
||||
@@ -1,157 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 1.6 to 1.7 for Red Hat Enterprise 7 or CentOS 7
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.6 to Scylla 1.7, and rollback to 1.6 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 1.6.x to Scylla version 1.7.y, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* drain node and backup the data
|
||||
* check your current release
|
||||
* backup configuration file
|
||||
* stop Scylla
|
||||
* download and install new Scylla packages
|
||||
* start 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.7 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.6
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <upgrade-1.6-1.7-rpm-rollback-procedure>` the upgrade. If you are not running a 1.6.x version, stop right here! This guide only covers 1.6.x to 1.7.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/centos_rpm>`_ to **1.7**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-1.6-1.7-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.7.x to 1.6.y. Apply this procedure if an upgrade from 1.6 to 1.7 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 1.7
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 1.6, you will:
|
||||
|
||||
* drain the node and stop Scylla
|
||||
* retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/centos_rpm>`_ to **1.6**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum downgrade scylla\* -y
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.6 /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 14.04 or 16.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-1.6-to-1.7/upgrade-guide-from-1.6-to-1.7-ubuntu/#upgrade-1-6-1-7-rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/#fndtn-deb
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-1.6-to-1.7-ubuntu-and-debian.rst
|
||||
@@ -1,43 +0,0 @@
|
||||
=================================
|
||||
Upgrade Guide - Scylla 1.7 to 2.0
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.7-to-2.0-rpm>
|
||||
Ubuntu <upgrade-guide-from-1.7-to-2.0-ubuntu>
|
||||
Debian <upgrade-guide-from-1.7-to-2.0-debian>
|
||||
Metrics <metric-update-1.7-to-2.0>
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla from 1.7 to 2.0</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 1.7.x to 2.0.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-1.7-to-2.0-rpm>`
|
||||
* :doc:`Upgrade Scylla from 1.7.x to 2.0.y on Ubuntu <upgrade-guide-from-1.7-to-2.0-ubuntu>`
|
||||
* :doc:`Upgrade Scylla from 1.7.x to 2.0.y on Debian <upgrade-guide-from-1.7-to-2.0-debian>`
|
||||
* :doc:`Scylla Metrics Update - Scylla 1.7 to 2.0<metric-update-1.7-to-2.0>`
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,66 +0,0 @@
|
||||
|
||||
|
||||
========================================
|
||||
Scylla Metric Update - Scylla 1.7 to 2.0
|
||||
========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
The following metric names have changed
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* scylla_cache_evictions To scylla_cache_partition_evictions
|
||||
* scylla_cache_hits To scylla_cache_partition_hits
|
||||
* scylla_cache_insertions To scylla_cache_partition_insertions
|
||||
* scylla_cache_merges To scylla_cache_partition_merges
|
||||
* scylla_cache_misses To scylla_cache_partition_misses
|
||||
* scylla_cache_removals To scylla_cache_partition_removals
|
||||
* scylla_cache_total To scylla_cache_bytes_total
|
||||
* scylla_cache_used To scylla_cache_bytes_used
|
||||
|
||||
The following metrics are no longer available
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* scylla_cache_uncached_wide_partitions
|
||||
* scylla_cache_wide_partition_evictions
|
||||
* scylla_cache_wide_partition_mispopulations
|
||||
|
||||
The following metrics are new in Scylla 2.0
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* scylla_cache_mispopulations
|
||||
* scylla_cache_reads
|
||||
* scylla_cache_active_reads
|
||||
* scylla_cache_reads_with_misses
|
||||
* scylla_cache_row_hits
|
||||
* scylla_cache_row_insertions
|
||||
* scylla_cache_row_misses
|
||||
* scylla_cache_sstable_partition_skips
|
||||
* scylla_cache_sstable_reader_recreations
|
||||
* scylla_cache_sstable_row_skips
|
||||
* scylla_column_family_live_disk_space
|
||||
* scylla_column_family_live_sstable
|
||||
* scylla_column_family_memtable_switch
|
||||
* scylla_column_family_pending_compaction
|
||||
* scylla_column_family_pending_tasks
|
||||
* scylla_column_family_total_disk_space
|
||||
* scylla_database_active_reads_streaming
|
||||
* scylla_database_counter_cell_lock_acquisition
|
||||
* scylla_database_counter_cell_lock_pending
|
||||
* scylla_database_cpu_flush_quota
|
||||
* scylla_database_queued_reads_streaming
|
||||
* scylla_execution_stages_function_calls_enqueued
|
||||
* scylla_execution_stages_function_calls_executed
|
||||
* scylla_execution_stages_tasks_preempted
|
||||
* scylla_execution_stages_tasks_scheduled
|
||||
* scylla_scylladb_current_version
|
||||
* scylla_sstables_index_page_blocks
|
||||
* scylla_sstables_index_page_hits
|
||||
* scylla_sstables_index_page_misses
|
||||
* scylla_storage_proxy_coordinator_background_read_repairs
|
||||
* scylla_storage_proxy_coordinator_foreground_read_repair
|
||||
* scylla_storage_proxy_coordinator_read_latency
|
||||
* scylla_storage_proxy_coordinator_write_latency
|
||||
* scylla_storage_proxy_replica_received_counter_updates
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Debian 8
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-1.7-to-2.0/upgrade-guide-from-1.7-to-2.0-debian/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/debian8/
|
||||
.. |ENABLE_APT_REPO| replace:: echo 'deb http://http.debian.net/debian jessie-backports main' > /etc/apt/sources.list.d/jessie-backports.list
|
||||
.. |JESSIE_BACKPORTS| replace:: -t jessie-backports openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-1.7-to-2.0-ubuntu-and-debian.rst
|
||||
@@ -1,178 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 1.7 to 2.0 for Red Hat Enterprise Linux 7 or CentOS 7
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.7 to Scylla 2.0, and rollback to 1.7 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 1.7.x (x >= 4) to Scylla version 2.0.y, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* check cluster schema
|
||||
* drain node and backup the data
|
||||
* backup configuration file
|
||||
* stop Scylla
|
||||
* download and install new Scylla packages
|
||||
* start 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 2.0 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.7
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <upgrade-1.7-2.0-rpm-rollback-procedure>` the upgrade. If you are not running a 1.7.x version, stop right here! This guide only covers 1.7.x to 2.0.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/?platform=centos>`_ to **2.0**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
* More on :doc:`Scylla Metrics Update - Scylla 1.7 to 2.0<metric-update-1.7-to-2.0>`
|
||||
|
||||
.. _upgrade-1.7-2.0-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 2.0.x to 1.7.y (y >= 4). Apply this procedure if an upgrade from 1.7 to 2.0 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2.0
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 1.7, you will:
|
||||
|
||||
* drain the node and stop Scylla
|
||||
* retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/?platform=centos>`_ to **1.7**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum remove scylla-tools-core
|
||||
sudo yum downgrade scylla\* -y
|
||||
sudo yum install scylla
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.7 /etc/scylla/scylla.yaml
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, 2.0 uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 14.04 or 16.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-1.7-to-2.0/upgrade-guide-from-1.7-to-2.0-ubuntu/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-1.7-to-2.0-ubuntu-and-debian.rst
|
||||
@@ -1,17 +0,0 @@
|
||||
=================================================
|
||||
Upgrade Guide - Scylla Maintenance Release
|
||||
=================================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux, and CentOS <upgrade-guide-from-1.x.y-to-1.x.z-rpm>
|
||||
Ubuntu <upgrade-guide-from-1.x.y-to-1.x.z-ubuntu>
|
||||
Debian <upgrade-guide-from-1.x.y-to-1.x.z-debian>
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 1.x.y to 1.x.z on Red Hat Enterprise Linux, and CentOS <upgrade-guide-from-1.x.y-to-1.x.z-rpm>`
|
||||
* :doc:`Upgrade Scylla from 1.x.y to 1.x.z on Ubuntu <upgrade-guide-from-1.x.y-to-1.x.z-ubuntu>`
|
||||
* :doc:`Upgrade Scylla from 1.x.y to 1.x.z on Debian <upgrade-guide-from-1.x.y-to-1.x.z-debian>`
|
||||
@@ -1,6 +0,0 @@
|
||||
.. |OS| replace:: Debian 8
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-1.x.y-to-1.x.z/upgrade-guide-from-1.x.y-to-1.x.z-debian/#upgrade-1.x.y-1.x.z-rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/#fndtn-Debian
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-1.x.y-to-1.x.z-ubuntu-and-debian.rst
|
||||
@@ -1,156 +0,0 @@
|
||||
==========================================================================
|
||||
Upgrade Guide - Scylla 1.x.y to 1.x.z for Red Hat Enterprise 7 or CentOS 7
|
||||
==========================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 1.x.y to Scylla 1.x.z.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 1.x.y to Scylla version 1.x.z, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* drain node and backup the data
|
||||
* check your current release
|
||||
* backup configuration file and rpm packages
|
||||
* stop Scylla
|
||||
* download and install new Scylla packages
|
||||
* start 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.x.z features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file and rpm packages
|
||||
------------------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-1.x.z
|
||||
|
||||
If you install scylla by yum, you can find the rpm packages in ``/var/cache/yum/``, backup scylla packages to ``scylla_1.x.y_backup`` directory which will be used in rollback.
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <upgrade-1.x.y-to-1.x.z-rpm-rollback-procedure>` the upgrade. If you are not running a 1.x.y version, stop right here! This guide only covers 1.x.y to 1.x.z upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/#fndtn-RPM>`_ to **1.x**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-1.x.y-to-1.x.z-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 1.x.z to 1.x.y. Apply this procedure if an upgrade from 1.x.y to 1.x.z failed before completing on all nodes. Use this procedure only for nodes you upgraded to 1.x.z
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 1.x.y, you will:
|
||||
|
||||
* drain the node and stop Scylla
|
||||
* retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Install the old release from backuped rpm packages
|
||||
--------------------------------------------------
|
||||
1. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum remove scylla\* -y
|
||||
sudo yum install scylla_1.x.y_backup/scylla*.rpm
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-1.x.z /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,6 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 14.04 or 16.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-1.x.y-to-1.x.z/upgrade-guide-from-1.x.y-to-1.x.z-ubuntu/#upgrade-1-x-y-1-x-z-rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/#fndtn-deb
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-1.x.y-to-1.x.z-ubuntu-and-debian.rst
|
||||
@@ -1,37 +0,0 @@
|
||||
=================================
|
||||
Upgrade Guide - Scylla 2.0 to 2.1
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-2.0-to-2.1-rpm>
|
||||
Ubuntu <upgrade-guide-from-2.0-to-2.1-ubuntu>
|
||||
Debian <upgrade-guide-from-2.0-to-2.1-debian>
|
||||
Metrics <metric-update-2.0-to-2.1>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla from 2.0 to 2.1</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 2.0.x to 2.1.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-2.0-to-2.1-rpm>`
|
||||
* :doc:`Upgrade Scylla from 2.0.x to 2.1.y on Ubuntu <upgrade-guide-from-2.0-to-2.1-ubuntu>`
|
||||
* :doc:`Upgrade Scylla from 2.0.x to 2.1.y on Debian <upgrade-guide-from-2.0-to-2.1-debian>`
|
||||
* :doc:`Scylla Metrics Update - Scylla 2.0 to 2.1<metric-update-2.0-to-2.1>`
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1,47 +0,0 @@
|
||||
|
||||
|
||||
Scylla Metric Update - Scylla 2.0 to 2.1
|
||||
========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
The following metric names have changed
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* Scylla_database_active_reads_streaming changed To scylla_database_active_reads {reads=streaming}
|
||||
* Scylla_database_active_reads_system_keyspace changed To scylla_database_active_reads {reads=system_keyspace}
|
||||
* scylla_database_queued_reads_streaming changed To scylla_database_queued_reads {reads=streaming}
|
||||
* scylla_database_queued_reads_system_keyspace changed To scylla_database_queued_reads_system {reads=keyspace}
|
||||
|
||||
The following metrics are new in Scylla 2.1
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* scylla_cache_pinned_dirty_memory_overload
|
||||
* scylla_column_family_cache_hit_rate
|
||||
* scylla_column_family_live_disk_space
|
||||
* scylla_column_family_live_sstable
|
||||
* scylla_column_family_memtable_switch
|
||||
* scylla_column_family_pending_compaction
|
||||
* scylla_column_family_pending_tasks
|
||||
* scylla_column_family_read_latency
|
||||
* scylla_column_family_total_disk_space
|
||||
* scylla_column_family_write_latency
|
||||
* scylla_cql_prepared_cache_evictions
|
||||
* scylla_cql_prepared_cache_memory_footprint
|
||||
* scylla_cql_prepared_cache_size
|
||||
* scylla_database_active_reads_memory_consumption
|
||||
* scylla_io_queue_commitlog_shares
|
||||
* scylla_io_queue_compaction_shares
|
||||
* scylla_io_queue_default_shares
|
||||
* scylla_io_queue_memtable_flush_shares
|
||||
* scylla_scheduler_queue_length
|
||||
* scylla_scheduler_runtime_ms
|
||||
* scylla_scheduler_shares
|
||||
* scylla_scheduler_tasks_processed
|
||||
* scylla_storage_proxy_coordinator_speculative_data_reads
|
||||
* scylla_storage_proxy_coordinator_speculative_digest_reads
|
||||
* scylla_storage_proxy_coordinator_total_write_attempts_remote_node
|
||||
* scylla_transport_requests_blocked_memory_current
|
||||
* scylla_transport_unpaged_queries
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Debian 8
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.0-to-2.1/upgrade-guide-from-2.0-to-2.1-debian/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/debian8/
|
||||
.. |ENABLE_APT_REPO| replace:: echo 'deb http://http.debian.net/debian jessie-backports main' > /etc/apt/sources.list.d/jessie-backports.list
|
||||
.. |JESSIE_BACKPORTS| replace:: -t jessie-backports openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.0-to-2.1-ubuntu-and-debian.rst
|
||||
@@ -1,179 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 2.0 to 2.1 for Red Hat Enterprise Linux 7 or CentOS 7
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 2.0 to Scylla 2.1, and rollback to 2.0 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 2.0.x to Scylla version 2.1.y, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 2.1 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-2.0
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <upgrade-2.0-2.1-rpm-rollback-procedure>` the upgrade. If you are not running a 2.0.x version, stop right here! This guide only covers 2.0.x to 2.1.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/?platform=centos>`_ to **2.1**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
* More on :doc:`Scylla Metrics Update - Scylla 2.0 to 2.1<metric-update-2.0-to-2.1>`
|
||||
|
||||
.. _upgrade-2.0-2.1-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 2.1.x to 2.0.y. Apply this procedure if an upgrade from 2.0 to 2.1 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2.1
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 2.0, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/?platform=centos>`_ to **2.0**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum remove scylla-tools-core
|
||||
sudo yum downgrade scylla\* -y
|
||||
sudo yum install scylla
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-2.0 /etc/scylla/scylla.yaml
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, 2.1 uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 14.04 or 16.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.0-to-2.1/upgrade-guide-from-2.0-to-2.1-ubuntu/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.0-to-2.1-ubuntu-and-debian.rst
|
||||
@@ -1,38 +0,0 @@
|
||||
=================================
|
||||
Upgrade Guide - Scylla 2.1 to 2.2
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-2.1-to-2.2-rpm>
|
||||
Ubuntu <upgrade-guide-from-2.1-to-2.2-ubuntu>
|
||||
Debian <upgrade-guide-from-2.1-to-2.2-debian>
|
||||
Metrics <metric-update-2.1-to-2.2>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla from 2.1 to 2.2</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 2.1.x to 2.2.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-2.1-to-2.2-rpm>`
|
||||
* :doc:`Upgrade Scylla from 2.1.x to 2.2.y on Ubuntu <upgrade-guide-from-2.1-to-2.2-ubuntu>`
|
||||
* :doc:`Upgrade Scylla from 2.1.x to 2.2.y on Debian <upgrade-guide-from-2.1-to-2.2-debian>`
|
||||
* :doc:`Scylla Metrics Update - Scylla 2.1 to 2.2<metric-update-2.1-to-2.2>`
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1,41 +0,0 @@
|
||||
|
||||
|
||||
Scylla Metric Update - Scylla 2.1 to 2.2
|
||||
========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Scylla 2.2 Dashboards are available as part of the latest |mon_root|
|
||||
|
||||
The following metrics are new in Scylla 2.2
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
* scylla_cache_row_evictions
|
||||
* scylla_cache_row_removals
|
||||
* scylla_cache_rows
|
||||
* scylla_cache_rows_dropped_from_memtable
|
||||
* scylla_cache_rows_merged_from_memtable
|
||||
* scylla_cache_rows_processed_from_memtable
|
||||
* scylla_cache_static_row_insertions
|
||||
* scylla_database_querier_cache_drops
|
||||
* scylla_database_querier_cache_lookups
|
||||
* scylla_database_querier_cache_memory_based_evictions
|
||||
* scylla_database_querier_cache_misses
|
||||
* scylla_database_querier_cache_population
|
||||
* scylla_database_querier_cache_resource_based_evictions
|
||||
* scylla_database_querier_cache_time_based_evictions
|
||||
* scylla_database_requests_blocked_memory_current
|
||||
* scylla_io_queue_commitlog_shares
|
||||
* scylla_io_queue_compaction_shares
|
||||
* scylla_io_queue_default_shares
|
||||
* scylla_io_queue_memtable_flush_shares
|
||||
* scylla_storage_proxy_coordinator_speculative_data_reads
|
||||
* scylla_storage_proxy_coordinator_speculative_digest_reads
|
||||
* scylla_transport_requests_blocked_memory_current
|
||||
|
||||
|
||||
The following metric was removed in Scylla 2.2
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
* scylla_database_cpu_flush_quota
|
||||
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Debian 8
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.1-to-2.2/upgrade-guide-from-2.1-to-2.2-debian/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/debian8/
|
||||
.. |ENABLE_APT_REPO| replace:: echo 'deb http://http.debian.net/debian jessie-backports main' > /etc/apt/sources.list.d/jessie-backports.list
|
||||
.. |JESSIE_BACKPORTS| replace:: -t jessie-backports openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.1-to-2.2-ubuntu-and-debian.rst
|
||||
@@ -1,178 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 2.1 to 2.2 for Red Hat Enterprise Linux 7 or CentOS 7
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 2.1 to Scylla 2.2, and rollback to 2.1 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 2.1.x to Scylla version 2.2.y, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 2.2 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
for conf in $( rpm -qc $(rpm -qa | grep scylla) | grep -v contains ); do sudo cp -v $conf $conf.backup-2.1; done
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <upgrade-2.1-2.2-rpm-rollback-procedure>` the upgrade. If you are not running a 2.1.x version, stop right here! This guide only covers 2.1.x to 2.2.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/?platform=centos>`_ to **2.2**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
* More on :doc:`Scylla Metrics Update - Scylla 2.1 to 2.2<metric-update-2.1-to-2.2>`
|
||||
|
||||
.. _upgrade-2.1-2.2-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 2.2.x to 2.1.y. Apply this procedure if an upgrade from 2.1 to 2.2 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2.2
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 2.1, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/?platform=centos>`_ to **2.1**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum remove scylla\*-tools-core scylla-libgcc73 scylla-libstdc++73 -y
|
||||
sudo yum downgrade scylla\* -y
|
||||
sudo yum install scylla
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
for conf in $( rpm -qc $(rpm -qa | grep scylla) | grep -v contains ); do sudo cp -v $conf.backup-2.1 $conf; done
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, 2.2 uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 14.04 or 16.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.1-to-2.2/upgrade-guide-from-2.1-to-2.2-ubuntu/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.1-to-2.2-ubuntu-and-debian.rst
|
||||
@@ -1,38 +0,0 @@
|
||||
==========================================
|
||||
Upgrade Guide - Scylla 2.2 to 2.3 (latest)
|
||||
==========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-2.2-to-2.3-rpm>
|
||||
Ubuntu <upgrade-guide-from-2.2-to-2.3-ubuntu>
|
||||
Ubuntu 16.04 <upgrade-guide-from-2.2-to-2.3-ubuntu-16-04>
|
||||
Debian <upgrade-guide-from-2.2-to-2.3-debian>
|
||||
Metrics <metric-update-2.2-to-2.3>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 2.2.y to 2.3.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-2.2-to-2.3-rpm>`
|
||||
* :doc:`Upgrade Scylla from 2.2.x to 2.3.y on Ubuntu 14.04 <upgrade-guide-from-2.2-to-2.3-ubuntu>`
|
||||
* :doc:`Upgrade Scylla from 2.2.x to 2.3.y on Ubuntu 16.04 <upgrade-guide-from-2.2-to-2.3-ubuntu-16-04>`
|
||||
* :doc:`Upgrade Scylla from 2.2.x to 2.3.y on Debian <upgrade-guide-from-2.2-to-2.3-debian>`
|
||||
* :doc:`Scylla Metrics Update - Scylla 2.2 to 2.3<metric-update-2.2-to-2.3>`
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -1,56 +0,0 @@
|
||||
|
||||
|
||||
Scylla Metric Update - Scylla 2.2 to 2.3
|
||||
========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Scylla 2.3 Dashboards are available as part of the latest |mon_root|
|
||||
|
||||
The following metrics are new in Scylla 2.3
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* scylla_cql_authorized_prepared_statements_cache_evictions
|
||||
* scylla_cql_authorized_prepared_statements_cache_size
|
||||
* scylla_cql_rows_read
|
||||
* scylla_cql_secondary_index_creates
|
||||
* scylla_cql_secondary_index_drops
|
||||
* scylla_cql_secondary_index_reads
|
||||
* scylla_cql_secondary_index_rows_read
|
||||
* scylla_cql_user_prepared_auth_cache_footprint
|
||||
* scylla_hints_for_views_manager_dropped
|
||||
* scylla_hints_for_views_manager_errors
|
||||
* scylla_hints_for_views_manager_sent
|
||||
* scylla_hints_for_views_manager_size_of_hints_in_progress
|
||||
* scylla_hints_for_views_manager_written
|
||||
* scylla_lsa_memory_allocated
|
||||
* scylla_lsa_memory_compacted
|
||||
* scylla_lsa_free_space
|
||||
* scylla_reactor_cpu_steal_time_ms
|
||||
|
||||
The following metrics were updated from Scylla 2.2 to Scylla 2.3
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* scylla_reactor_cpu_busy_ns changed to scylla_reactor_cpu_busy_ms
|
||||
* scylla_storage_proxy_coordinator_read_latency is split into:
|
||||
|
||||
* scylla_storage_proxy_coordinator_read_latency_bucket
|
||||
* scylla_storage_proxy_coordinator_read_latency_count
|
||||
* scylla_storage_proxy_coordinator_read_latency_sum
|
||||
|
||||
* scylla_storage_proxy_coordinator_write_latency changed is split into:
|
||||
|
||||
* scylla_storage_proxy_coordinator_write_latency_bucket
|
||||
* scylla_storage_proxy_coordinator_write_latency_count
|
||||
* scylla_storage_proxy_coordinator_write_latency_sum
|
||||
|
||||
|
||||
|
||||
The following metrics were removed in Scylla 2.3
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* scylla_lsa_zones
|
||||
* scylla_lsa_free_space_in_zones
|
||||
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Debian 8
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.2-to-2.3/upgrade-guide-from-2.2-to-2.3-debian/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/debian8/
|
||||
.. |ENABLE_APT_REPO| replace:: echo 'deb http://http.debian.net/debian jessie-backports main' > /etc/apt/sources.list.d/jessie-backports.list
|
||||
.. |JESSIE_BACKPORTS| replace:: -t jessie-backports openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.2-to-2.3-ubuntu-and-debian.rst
|
||||
@@ -1,175 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 2.2 to 2.3 for Red Hat Enterprise Linux 7 or CentOS 7
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 2.2 to Scylla 2.3, and rollback to 2.2 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 2.2.x to Scylla version 2.3.y, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 2.3 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
for conf in $( rpm -qc $(rpm -qa | grep scylla) | grep -v contains ); do sudo cp -v $conf $conf.backup-2.2; done
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <upgrade-2.2-2.3-rpm-rollback-procedure>` the upgrade. If you are not running a 2.2.x version, stop right here! This guide only covers 2.2.x to 2.3.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/?platform=centos>`_ to **2.3**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
* More on :doc:`Scylla Metrics Update - Scylla 2.2 to 2.3<metric-update-2.2-to-2.3>`
|
||||
|
||||
.. _upgrade-2.2-2.3-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 2.3.x to 2.2.y. Apply this procedure if an upgrade from 2.2 to 2.3 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2.3
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 2.2, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/?platform=centos>`_ to **2.2**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo yum downgrade scylla\* -y
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
for conf in $( rpm -qc $(rpm -qa | grep scylla) | grep -v contains ); do sudo cp -v $conf.backup-2.2 $conf; done
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, 2.3 uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,10 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 16.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.2-to-2.3/upgrade-guide-from-2.2-to-2.3-ubuntu-16-04/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/
|
||||
.. |APT_ENTERPRISE| replace:: Scylla Enterprise Deb repo
|
||||
.. _APT_ENTERPRISE: http://www.scylladb.com/download/?platform=ubuntu-16.04
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.2-to-2.3-ubuntu-and-debian.rst
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 14.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.2-to-2.3/upgrade-guide-from-2.2-to-2.3-ubuntu/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.2-to-2.3-ubuntu-and-debian.rst
|
||||
@@ -1,40 +0,0 @@
|
||||
==========================================
|
||||
Upgrade Guide - Scylla 2.3 to 3.0
|
||||
==========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-2.3-to-3.0-rpm>
|
||||
Ubuntu <upgrade-guide-from-2.3-to-3.0-ubuntu>
|
||||
Ubuntu 16.04 <upgrade-guide-from-2.3-to-3.0-ubuntu-16-04>
|
||||
Ubuntu 18.04 <upgrade-guide-from-2.3-to-3.0-ubuntu-18-04>
|
||||
Debian <upgrade-guide-from-2.3-to-3.0-debian>
|
||||
Metrics <metric-update-2.3-to-3.0>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 2.3.y to 3.0.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-2.3-to-3.0-rpm>`
|
||||
* :doc:`Upgrade Scylla from 2.3.x to 3.0.y on Ubuntu 14.04 <upgrade-guide-from-2.3-to-3.0-ubuntu>`
|
||||
* :doc:`Upgrade Scylla from 2.3.x to 3.0.y on Ubuntu 16.04 <upgrade-guide-from-2.3-to-3.0-ubuntu-16-04>`
|
||||
* :doc:`Upgrade Scylla from 2.3.x to 3.0.y on Ubuntu 18.04 <upgrade-guide-from-2.3-to-3.0-ubuntu-18-04>`
|
||||
* :doc:`Upgrade Scylla from 2.3.x to 3.0.y on Debian <upgrade-guide-from-2.3-to-3.0-debian>`
|
||||
* :doc:`Scylla Metrics Update - Scylla 2.3 to 3.0<metric-update-2.3-to-3.0>`
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -1,35 +0,0 @@
|
||||
|
||||
|
||||
Scylla Metric Update - Scylla 2.3 to 3.0
|
||||
========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Scylla 3.0 Dashboards are available as part of the latest |mon_root|
|
||||
|
||||
The following metrics are new in Scylla 3.0
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* `scylla_cql_filtered_read_requests`
|
||||
* `scylla_cql_filtered_rows_dropped_total`
|
||||
* `scylla_cql_filtered_rows_matched_total`
|
||||
* `scylla_cql_filtered_rows_read_total`
|
||||
* `scylla_cql_reverse_queries`
|
||||
* `scylla_database_large_partition_exceeding_threshold`
|
||||
* `scylla_database_multishard_query_failed_reader_saves`
|
||||
* `scylla_database_multishard_query_failed_reader_stops`
|
||||
* `scylla_database_multishard_query_unpopped_bytes`
|
||||
* `scylla_database_multishard_query_unpopped_fragments`
|
||||
* `scylla_node_operation_mode`
|
||||
* `scylla_storage_proxy_replica_cross_shard_ops`
|
||||
|
||||
|
||||
The following metric was updated from Scylla 2.3 to Scylla 3.0
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* `scylla_reactor_cpu_busy_ns` changed to `scylla_reactor_cpu_busy_ms`
|
||||
* `scylla_reactor_cpu_steal_time_ns` changed to `scylla_reactor_cpu_steal_time_ms`
|
||||
* `scylla_scheduler_time_spent_on_task_quota_violations_ns` changed to `scylla_scheduler_time_spent_on_task_quota_violations_ms`
|
||||
* `scylla_transport_unpaged_queries` changed to `scylla_cql_unpaged_select_queries`
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Debian 8
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/upgrade-guide-from-2.3-to-3.0-debian/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/debian8/
|
||||
.. |ENABLE_APT_REPO| replace:: echo 'deb http://http.debian.net/debian jessie-backports main' > /etc/apt/sources.list.d/jessie-backports.list
|
||||
.. |JESSIE_BACKPORTS| replace:: -t jessie-backports openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.3-to-3.0-ubuntu-and-debian.rst
|
||||
@@ -1,193 +0,0 @@
|
||||
=============================================================================
|
||||
Upgrade Guide - Scylla 2.3 to 3.0 for Red Hat Enterprise Linux 7 or CentOS 7
|
||||
=============================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 2.3 to Scylla 3.0, and rollback to 2.3 if required.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 2.3.x to Scylla version 3.0.y, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* Check cluster schema
|
||||
* Drain node and backup the data
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 3.0 features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Check cluster schema
|
||||
--------------------
|
||||
Make sure that all nodes have the schema synched prior to upgrade, we won't survive an upgrade that has schema disagreement between nodes.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool describecluster
|
||||
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
.. code:: sh
|
||||
|
||||
for conf in $( rpm -qc $(rpm -qa | grep scylla) | grep -v contains ); do sudo cp -v $conf $conf.backup-2.3; done
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <upgrade-2.3-3.0-rpm-rollback-procedure>` the upgrade. If you are not running a 2.3.x version, stop right here! This guide only covers 2.3.x to 3.0.y upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/?platform=centos>`_ to **3.0**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
3. Upgrade node_exporter
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop node-exporter
|
||||
sudo rm /usr/bin/node_exporter
|
||||
sudo node_exporter_install
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
* More on :doc:`Scylla Metrics Update - Scylla 2.3 to 3.0<metric-update-2.3-to-3.0>`
|
||||
|
||||
.. _upgrade-2.3-3.0-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 3.0.x to 2.3.y. Apply this procedure if an upgrade from 2.3 to 3.0 failed before completing on all nodes. Use this procedure only for nodes you upgraded to 3.0
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 2.3, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Retrieve the old Scylla packages
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
1. Remove the old repo file.
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/yum.repos.d/scylla.repo
|
||||
|
||||
2. Update the `Scylla RPM repo <http://www.scylladb.com/download/?platform=centos>`_ to **2.3**
|
||||
3. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum clean all
|
||||
sudo rm -rf /var/cache/yum
|
||||
sudo yum downgrade scylla\* -y
|
||||
|
||||
3. Install old node_exporter
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop node-exporter
|
||||
sudo rm /usr/bin/node_exporter
|
||||
sudo node_exporter_install
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
for conf in $( rpm -qc $(rpm -qa | grep scylla) | grep -v contains ); do sudo cp -v $conf.backup-2.3 $conf; done
|
||||
|
||||
Restore system tables
|
||||
---------------------
|
||||
|
||||
Restore all tables of **system** and **system_schema** from previous snapshot, 3.0 uses a different set of system tables. Reference doc: :doc:`Restore from a Backup and Incremental Backup </operating-scylla/procedures/backup-restore/restore/>`
|
||||
|
||||
.. code:: sh
|
||||
|
||||
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/
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,10 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 16.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/upgrade-guide-from-2.3-to-3.0-ubuntu-16-04/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/
|
||||
.. |APT_ENTERPRISE| replace:: Scylla Enterprise Deb repo
|
||||
.. _APT_ENTERPRISE: http://www.scylladb.com/download/?platform=ubuntu-16.04
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.3-to-3.0-ubuntu-and-debian.rst
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 18.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/upgrade-guide-from-2.3-to-3.0-ubuntu-18-04/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/?platform=ubuntu-18.04
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.3-to-3.0-ubuntu-and-debian.rst
|
||||
@@ -1,8 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 14.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.3-to-3.0/upgrade-guide-from-2.3-to-3.0-ubuntu/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.3-to-3.0-ubuntu-and-debian.rst
|
||||
@@ -1,36 +0,0 @@
|
||||
=================================================
|
||||
Upgrade Guide - Scylla Maintenance Release
|
||||
=================================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-2.x.y-to-2.x.z-rpm>
|
||||
Ubuntu <upgrade-guide-from-2.x.y-to-2.x.z-ubuntu>
|
||||
Debian <upgrade-guide-from-2.x.y-to-2.x.z-debian>
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 2.x.y to 2.x.z on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-2.x.y-to-2.x.z-rpm>`
|
||||
* :doc:`Upgrade Scylla from 2.x.y to 2.x.z on Ubuntu <upgrade-guide-from-2.x.y-to-2.x.z-ubuntu>`
|
||||
* :doc:`Upgrade Scylla from 2.x.y to 2.x.z on Debian <upgrade-guide-from-2.x.y-to-2.x.z-debian>`
|
||||
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1,6 +0,0 @@
|
||||
.. |OS| replace:: Debian 8
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.x.y-to-2.x.z/upgrade-guide-from-2.x.y-to-2.x.z-debian/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/debian8/
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.x.y-to-2.x.z-ubuntu-and-debian.rst
|
||||
@@ -1,152 +0,0 @@
|
||||
==========================================================================
|
||||
Upgrade Guide - Scylla 2.x.y to 2.x.z for Red Hat Enterprise 7 or CentOS 7
|
||||
==========================================================================
|
||||
|
||||
This document is a step by step procedure for upgrading from Scylla 2.x.y to Scylla 2.x.z.
|
||||
|
||||
|
||||
Applicable versions
|
||||
===================
|
||||
This guide covers upgrading Scylla from the following versions: 2.x.y to Scylla version 2.x.z, on the following platforms:
|
||||
|
||||
* Red Hat Enterprise Linux, version 7 and later
|
||||
* CentOS, version 7 and later
|
||||
* No longer provide packages for Fedora
|
||||
|
||||
Upgrade Procedure
|
||||
=================
|
||||
|
||||
.. include:: /upgrade/_common/warning.rst
|
||||
|
||||
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:
|
||||
|
||||
* Drain node and backup the data
|
||||
* Check your current release
|
||||
* Backup configuration file
|
||||
* Stop Scylla
|
||||
* Download and install new Scylla packages
|
||||
* Start 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 2.x.z features
|
||||
* Not to run administration functions, like repairs, refresh, rebuild or add or remove nodes
|
||||
* Not to apply schema changes
|
||||
|
||||
Upgrade steps
|
||||
=============
|
||||
Drain node and backup the data
|
||||
------------------------------
|
||||
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:
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
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.
|
||||
|
||||
When the upgrade is complete (all nodes), the snapshot should be removed by ``nodetool clearsnapshot -t <snapshot>``, or you risk running out of space.
|
||||
|
||||
Backup configuration file
|
||||
-------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo cp -a /etc/scylla/scylla.yaml /etc/scylla/scylla.yaml.backup-2.x.z
|
||||
|
||||
Stop Scylla
|
||||
-----------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Download and install the new release
|
||||
------------------------------------
|
||||
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 :ref:`rollback <upgrade-2.x.y-to-2.x.z-rpm-rollback-procedure>` the upgrade. If you are not running a 2.x.y version, stop right here! This guide only covers 2.x.y to 2.x.z upgrades.
|
||||
|
||||
To upgrade:
|
||||
|
||||
1. Update the `Scylla RPM repo <http://www.scylladb.com/download/#fndtn-RPM>`_ to **2.x**
|
||||
2. install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum update scylla\* -y
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
1. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in UN status.
|
||||
2. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check scylla version.
|
||||
3. Use ``journalctl _COMM=scylla`` to check there are no new errors in the log.
|
||||
4. 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.
|
||||
|
||||
.. _upgrade-2.x.y-to-2.x.z-rpm-rollback-procedure:
|
||||
|
||||
Rollback Procedure
|
||||
==================
|
||||
|
||||
.. include:: /upgrade/_common/warning_rollback.rst
|
||||
|
||||
The following procedure describes a rollback from Scylla release 2.x.z to 2.x.y. Apply this procedure if an upgrade from 2.x.y to 2.x.z failed before completing on all nodes. Use this procedure only for nodes you upgraded to 2.x.z
|
||||
|
||||
Scylla rollback is a rolling procedure which does **not** require full cluster shutdown.
|
||||
For each of the nodes rollback to 2.x.y, you will:
|
||||
|
||||
* Drain the node and stop Scylla
|
||||
* Downgrade to previous release
|
||||
* 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.
|
||||
|
||||
Rollback steps
|
||||
==============
|
||||
Gracefully shutdown Scylla
|
||||
--------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
nodetool drain
|
||||
sudo systemctl stop scylla-server
|
||||
|
||||
Downgrade to previous release
|
||||
--------------------------------------------------
|
||||
1. Install
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo yum downgrade scylla\*-2.x.y
|
||||
|
||||
Restore the configuration file
|
||||
------------------------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo rm -rf /etc/scylla/scylla.yaml
|
||||
sudo cp -a /etc/scylla/scylla.yaml.backup-2.x.z /etc/scylla/scylla.yaml
|
||||
|
||||
Start the node
|
||||
--------------
|
||||
|
||||
.. code:: sh
|
||||
|
||||
sudo systemctl start scylla-server
|
||||
|
||||
Validate
|
||||
--------
|
||||
Check upgrade instruction above for validation. Once you are sure the node rollback is successful, move to the next node in the cluster.
|
||||
@@ -1,6 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 14.04 or 16.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: /upgrade/upgrade-opensource/upgrade-guide-from-2.x.y-to-2.x.z/upgrade-guide-from-2.x.y-to-2.x.z-ubuntu/#rollback-procedure
|
||||
.. |APT| replace:: Scylla deb repo
|
||||
.. _APT: http://www.scylladb.com/download/
|
||||
.. include:: /upgrade/_common/upgrade-guide-from-2.x.y-to-2.x.z-ubuntu-and-debian.rst
|
||||
@@ -1,38 +0,0 @@
|
||||
==========================================
|
||||
Upgrade Guide - Scylla 3.0 to 3.1
|
||||
==========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-3.0-to-3.1-rpm>
|
||||
Ubuntu 16.04 <upgrade-guide-from-3.0-to-3.1-ubuntu-16-04>
|
||||
Ubuntu 18.04 <upgrade-guide-from-3.0-to-3.1-ubuntu-18-04>
|
||||
Debian <upgrade-guide-from-3.0-to-3.1-debian>
|
||||
Metrics <metric-update-3.0-to-3.1>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 3.0.y to 3.1.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-3.0-to-3.1-rpm>`
|
||||
* :doc:`Upgrade Scylla from 3.0.x to 3.1.y on Ubuntu 16.04 <upgrade-guide-from-3.0-to-3.1-ubuntu-16-04>`
|
||||
* :doc:`Upgrade Scylla from 3.0.x to 3.1.y on Ubuntu 18.04 <upgrade-guide-from-3.0-to-3.1-ubuntu-18-04>`
|
||||
* :doc:`Upgrade Scylla from 3.0.x to 3.1.y on Debian <upgrade-guide-from-3.0-to-3.1-debian>`
|
||||
* :doc:`Scylla Metrics Update - Scylla 3.0 to 3.1<metric-update-3.0-to-3.1>`
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -1,118 +0,0 @@
|
||||
|
||||
|
||||
Scylla Metric Update - Scylla 3.0 to 3.1
|
||||
========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Scylla 3.1 Dashboards are available as part of the latest |mon_root|
|
||||
|
||||
|
||||
The following metrics are new in Scylla 3.1
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* `scylla_database_paused_reads`
|
||||
* `scylla_database_paused_reads_permit_based_evictions`
|
||||
* `scylla_database_total_view_updates_failed_local`
|
||||
* `scylla_database_total_view_updates_failed_remote`
|
||||
* `scylla_database_total_view_updates_pushed_local`
|
||||
* `scylla_database_total_view_updates_pushed_remote`
|
||||
* `scylla_database_view_building_paused`
|
||||
* `scylla_hints_for_views_manager_corrupted_files`
|
||||
* `scylla_hints_for_views_manager_discarded`
|
||||
* `scylla_hints_manager_corrupted_files`
|
||||
* `scylla_hints_manager_discarded`
|
||||
* `scylla_query_processor_queries`
|
||||
* `scylla_reactor_aio_errors`
|
||||
* `scylla_sstables_capped_local_deletion_time`
|
||||
* `scylla_sstables_capped_tombstone_deletion_time`
|
||||
* `scylla_sstables_cell_tombstone_writes`
|
||||
* `scylla_sstables_cell_writes`
|
||||
* `scylla_sstables_partition_reads`
|
||||
* `scylla_sstables_partition_seeks`
|
||||
* `scylla_sstables_partition_writes`
|
||||
* `scylla_sstables_range_partition_reads`
|
||||
* `scylla_sstables_range_tombstone_writes`
|
||||
* `scylla_sstables_row_reads`
|
||||
* `scylla_sstables_row_writes`
|
||||
* `scylla_sstables_single_partition_reads`
|
||||
* `scylla_sstables_sstable_partition_reads`
|
||||
* `scylla_sstables_static_row_writes`
|
||||
* `scylla_sstables_tombstone_writes`
|
||||
* `scylla_storage_proxy_coordinator_last_mv_flow_control_delay`
|
||||
|
||||
|
||||
The following metrics were updated from Scylla 3.0 to Scylla 3.1
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
In the metrics marked with an asterisk (*), the queue has become a label.
|
||||
|
||||
.. list-table::
|
||||
:widths: 30 30 30
|
||||
:header-rows: 1
|
||||
|
||||
* - Scylla 3.0 Name
|
||||
- Scylla 3.1 Name
|
||||
- Scylla 3.1 Class Label*
|
||||
* - scylla_io_queue_commitlog_delay
|
||||
- scylla_io_queue_delay
|
||||
- commitlog
|
||||
* - scylla_io_queue_commitlog_queue_length
|
||||
- scylla_io_queue_queue_length
|
||||
- commitlog
|
||||
* - scylla_io_queue_commitlog_shares
|
||||
- scylla_io_queue_shares
|
||||
- commitlog
|
||||
* - scylla_io_queue_commitlog_total_bytes
|
||||
- scylla_io_queue_total_bytes
|
||||
- commitlog
|
||||
* - scylla_io_queue_commitlog_total_operations
|
||||
- scylla_io_queue_total_operations
|
||||
- commitlog
|
||||
* - scylla_io_queue_compaction_delay
|
||||
- scylla_io_queue_delay
|
||||
- compaction
|
||||
* - scylla_io_queue_compaction_queue_length
|
||||
- scylla_io_queue_queue_length
|
||||
- compaction
|
||||
* - scylla_io_queue_compaction_shares
|
||||
- scylla_io_queue_shares
|
||||
- compaction
|
||||
* - scylla_io_queue_compaction_total_bytes
|
||||
- scylla_io_queue_total_bytes
|
||||
- compaction
|
||||
* - scylla_io_queue_compaction_total_operations
|
||||
- scylla_io_queue_total_operations
|
||||
- compaction
|
||||
* - scylla_io_queue_default_delay
|
||||
- scylla_io_queue_delay
|
||||
- default
|
||||
* - scylla_io_queue_default_queue_length
|
||||
- scylla_io_queue_queue_length
|
||||
- default
|
||||
* - scylla_io_queue_default_shares
|
||||
- scylla_io_queue_shares
|
||||
- default
|
||||
* - scylla_io_queue_default_total_bytes
|
||||
- scylla_io_queue_total_bytes
|
||||
- default
|
||||
* - scylla_io_queue_default_total_operations
|
||||
- scylla_io_queue_total_operations
|
||||
- default
|
||||
* - scylla_io_queue_memtable_flush_delay
|
||||
- scylla_io_queue_delay
|
||||
- memtable
|
||||
* - scylla_io_queue_memtable_flush_queue_length
|
||||
- scylla_io_queue_queue_length
|
||||
- memtable
|
||||
* - scylla_io_queue_memtable_flush_shares
|
||||
- scylla_io_queue_shares
|
||||
- memtable
|
||||
* - scylla_io_queue_memtable_flush_total_bytes
|
||||
- scylla_io_queue_total_bytes
|
||||
- memtable
|
||||
* - scylla_io_queue_memtable_flush_total_operations
|
||||
- scylla_io_queue_total_operations
|
||||
- memtable
|
||||
@@ -1,17 +0,0 @@
|
||||
.. |OS| replace:: Debian 9
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: ./#rollback-procedure
|
||||
.. |ENABLE_APT_REPO| replace:: echo 'deb http://http.debian.net/debian jessie-backports main' > /etc/apt/sources.list.d/jessie-backports.list
|
||||
.. |JESSIE_BACKPORTS| replace:: -t jessie-backports openjdk-8-jre-headless
|
||||
.. |OPENJDK| replace:: openjdk-8-jre-headless
|
||||
.. |SRC_VERSION| replace:: 3.0
|
||||
.. |NEW_VERSION| replace:: 3.1
|
||||
.. |SCYLLA_NAME| replace:: Scylla
|
||||
.. |PKG_NAME| replace:: scylla
|
||||
.. |SCYLLA_REPO| replace:: Scylla deb repo
|
||||
.. _SCYLLA_REPO: http://www.scylladb.com/download/?platform=debian-9
|
||||
.. |SCYLLA_METRICS| replace:: Scylla Metrics Update - Scylla 3.0 to 3.1
|
||||
.. _SCYLLA_METRICS: ../metric-update-3.0-to-3.1
|
||||
.. |SCYLLA_MONITOR| replace:: Scylla Monitoring 2.4
|
||||
.. _SCYLLA_MONITOR: /operating-scylla/monitoring/
|
||||
.. include:: /upgrade/_common/upgrade-guide-v1-ubuntu-and-debian.rst
|
||||
@@ -1,11 +0,0 @@
|
||||
.. |SRC_VERSION| replace:: 3.0
|
||||
.. |NEW_VERSION| replace:: 3.1
|
||||
.. |SCYLLA_NAME| replace:: Scylla
|
||||
.. |PKG_NAME| replace:: scylla
|
||||
.. |SCYLLA_REPO| replace:: Scylla rpm repo
|
||||
.. _SCYLLA_REPO: http://www.scylladb.com/download/?platform=centos
|
||||
.. |SCYLLA_METRICS| replace:: Scylla Metrics Update - Scylla 3.0 to 3.1
|
||||
.. _SCYLLA_METRICS: ../metric-update-3.0-to-3.1
|
||||
.. |SCYLLA_MONITOR| replace:: Scylla Monitoring 2.4
|
||||
.. _SCYLLA_MONITOR: /operating-scylla/monitoring/
|
||||
.. include:: /upgrade/_common/upgrade-guide-v1-rpm.rst
|
||||
@@ -1,17 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 16.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: ./#rollback-procedure
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. |OPENJDK| replace:: openjdk-8-jre-headless
|
||||
.. |SRC_VERSION| replace:: 3.0
|
||||
.. |NEW_VERSION| replace:: 3.1
|
||||
.. |SCYLLA_NAME| replace:: Scylla
|
||||
.. |PKG_NAME| replace:: scylla
|
||||
.. |SCYLLA_REPO| replace:: Scylla deb repo
|
||||
.. _SCYLLA_REPO: http://www.scylladb.com/download/?platform=ubuntu-16.04
|
||||
.. |SCYLLA_METRICS| replace:: Scylla Metrics Update - Scylla 3.0 to 3.1
|
||||
.. _SCYLLA_METRICS: ../metric-update-3.0-to-3.1
|
||||
.. |SCYLLA_MONITOR| replace:: Scylla Monitoring 2.4
|
||||
.. _SCYLLA_MONITOR: /operating-scylla/monitoring/
|
||||
.. include:: /upgrade/_common/upgrade-guide-v1-ubuntu-and-debian.rst
|
||||
@@ -1,17 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 18.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: ./#rollback-procedure
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. |OPENJDK| replace:: openjdk-8-jre-headless
|
||||
.. |SRC_VERSION| replace:: 3.0
|
||||
.. |NEW_VERSION| replace:: 3.1
|
||||
.. |SCYLLA_NAME| replace:: Scylla
|
||||
.. |PKG_NAME| replace:: scylla
|
||||
.. |SCYLLA_REPO| replace:: Scylla deb repo
|
||||
.. _SCYLLA_REPO: http://www.scylladb.com/download/?platform=ubuntu-18.04
|
||||
.. |SCYLLA_METRICS| replace:: Scylla Metrics Update - Scylla 3.0 to 3.1
|
||||
.. _SCYLLA_METRICS: ../metric-update-3.0-to-3.1
|
||||
.. |SCYLLA_MONITOR| replace:: Scylla Monitoring 2.4
|
||||
.. _SCYLLA_MONITOR: /operating-scylla/monitoring/
|
||||
.. include:: /upgrade/_common/upgrade-guide-v1-ubuntu-and-debian.rst
|
||||
@@ -1,38 +0,0 @@
|
||||
=================================
|
||||
Upgrade Guide - Scylla 3.1 to 3.2
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-3.1-to-3.2-rpm>
|
||||
Ubuntu 16.04 <upgrade-guide-from-3.1-to-3.2-ubuntu-16-04>
|
||||
Ubuntu 18.04 <upgrade-guide-from-3.1-to-3.2-ubuntu-18-04>
|
||||
Debian <upgrade-guide-from-3.1-to-3.2-debian>
|
||||
Metrics <metric-update-3.1-to-3.2>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 3.1.y to 3.2.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-3.1-to-3.2-rpm>`
|
||||
* :doc:`Upgrade Scylla from 3.1.x to 3.2.y on Ubuntu 16.04 <upgrade-guide-from-3.1-to-3.2-ubuntu-16-04>`
|
||||
* :doc:`Upgrade Scylla from 3.1.x to 3.2.y on Ubuntu 18.04 <upgrade-guide-from-3.1-to-3.2-ubuntu-18-04>`
|
||||
* :doc:`Upgrade Scylla from 3.1.x to 3.2.y on Debian <upgrade-guide-from-3.1-to-3.2-debian>`
|
||||
* :doc:`Scylla Metrics Update - Scylla 3.1 to 3.2<metric-update-3.1-to-3.2>`
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -1,43 +0,0 @@
|
||||
|
||||
|
||||
Scylla Metric Update - Scylla 3.1 to 3.2
|
||||
========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Scylla 3.2 Dashboards are available as part of the latest |mon_root|.
|
||||
|
||||
The following metrics are new in Scylla 3.2
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* `scylla_database_schema_changed`
|
||||
* `scylla_memtables_failed_flushes`
|
||||
* `scylla_storage_proxy_coordinator_cas_read_contention`
|
||||
* `scylla_storage_proxy_coordinator_cas_read_latency`
|
||||
* `scylla_storage_proxy_coordinator_cas_read_timeouts`
|
||||
* `scylla_storage_proxy_coordinator_cas_read_unavailable`
|
||||
* `scylla_storage_proxy_coordinator_cas_read_unfinished_commit`
|
||||
* `scylla_storage_proxy_coordinator_cas_write_condition_not_met`
|
||||
* `scylla_storage_proxy_coordinator_cas_write_contention`
|
||||
* `scylla_storage_proxy_coordinator_cas_write_latency`
|
||||
* `scylla_storage_proxy_coordinator_cas_write_timeouts`
|
||||
* `scylla_storage_proxy_coordinator_cas_write_unavailable`
|
||||
* `scylla_storage_proxy_coordinator_cas_write_unfinished_commit`
|
||||
* `scylla_storage_proxy_coordinator_reads_coordinator_outside_replica_set`
|
||||
* `scylla_storage_proxy_coordinator_writes_coordinator_outside_replica_set`
|
||||
* `scylla_transport_requests_memory_available`
|
||||
|
||||
|
||||
The following metric was updated from Scylla 3.1 to Scylla 3.2
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. list-table::
|
||||
:widths: 30 30
|
||||
:header-rows: 1
|
||||
|
||||
* - Scylla 3.1 Name
|
||||
- Scylla 3.2 Name
|
||||
* - scylla_storage_proxy_coordinator_foreground_read_repair
|
||||
- scylla_storage_proxy_coordinator_foreground_read_repairs
|
||||
@@ -1,17 +0,0 @@
|
||||
.. |OS| replace:: Debian 9
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: ./#rollback-procedure
|
||||
.. |ENABLE_APT_REPO| replace:: echo 'deb http://http.debian.net/debian jessie-backports main' > /etc/apt/sources.list.d/jessie-backports.list
|
||||
.. |JESSIE_BACKPORTS| replace:: -t jessie-backports openjdk-8-jre-headless
|
||||
.. |OPENJDK| replace:: openjdk-8-jre-headless
|
||||
.. |SRC_VERSION| replace:: 3.1
|
||||
.. |NEW_VERSION| replace:: 3.2
|
||||
.. |SCYLLA_NAME| replace:: Scylla
|
||||
.. |PKG_NAME| replace:: scylla
|
||||
.. |SCYLLA_REPO| replace:: Scylla deb repo
|
||||
.. _SCYLLA_REPO: http://www.scylladb.com/download/?platform=debian-9
|
||||
.. |SCYLLA_METRICS| replace:: Scylla Metrics Update - Scylla 3.1 to 3.2
|
||||
.. _SCYLLA_METRICS: ../metric-update-3.1-to-3.2
|
||||
.. |SCYLLA_MONITOR| replace:: Scylla Monitoring 3.0
|
||||
.. _SCYLLA_MONITOR: /operating-scylla/monitoring/
|
||||
.. include:: /upgrade/_common/upgrade-guide-v2-ubuntu-and-debian.rst
|
||||
@@ -1,11 +0,0 @@
|
||||
.. |SRC_VERSION| replace:: 3.1
|
||||
.. |NEW_VERSION| replace:: 3.2
|
||||
.. |SCYLLA_NAME| replace:: Scylla
|
||||
.. |PKG_NAME| replace:: scylla
|
||||
.. |SCYLLA_REPO| replace:: Scylla rpm repo
|
||||
.. _SCYLLA_REPO: http://www.scylladb.com/download/?platform=centos
|
||||
.. |SCYLLA_METRICS| replace:: Scylla Metrics Update - Scylla 3.1 to 3.2
|
||||
.. _SCYLLA_METRICS: ../metric-update-3.1-to-3.2
|
||||
.. |SCYLLA_MONITOR| replace:: Scylla Monitoring 3.0
|
||||
.. _SCYLLA_MONITOR: /operating-scylla/monitoring/
|
||||
.. include:: /upgrade/_common/upgrade-guide-v2-rpm.rst
|
||||
@@ -1,17 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 16.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: ./#rollback-procedure
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. |OPENJDK| replace:: openjdk-8-jre-headless
|
||||
.. |SRC_VERSION| replace:: 3.1
|
||||
.. |NEW_VERSION| replace:: 3.2
|
||||
.. |SCYLLA_NAME| replace:: Scylla
|
||||
.. |PKG_NAME| replace:: scylla
|
||||
.. |SCYLLA_REPO| replace:: Scylla deb repo
|
||||
.. _SCYLLA_REPO: http://www.scylladb.com/download/?platform=ubuntu-16.04
|
||||
.. |SCYLLA_METRICS| replace:: Scylla Metrics Update - Scylla 3.1 to 3.2
|
||||
.. _SCYLLA_METRICS: ../metric-update-3.1-to-3.2
|
||||
.. |SCYLLA_MONITOR| replace:: Scylla Monitoring 3.0
|
||||
.. _SCYLLA_MONITOR: /operating-scylla/monitoring/
|
||||
.. include:: /upgrade/_common/upgrade-guide-v2-ubuntu-and-debian.rst
|
||||
@@ -1,17 +0,0 @@
|
||||
.. |OS| replace:: Ubuntu 18.04
|
||||
.. |ROLLBACK| replace:: rollback
|
||||
.. _ROLLBACK: ./#rollback-procedure
|
||||
.. |ENABLE_APT_REPO| replace:: sudo add-apt-repository -y ppa:openjdk-r/ppa
|
||||
.. |JESSIE_BACKPORTS| replace:: openjdk-8-jre-headless
|
||||
.. |OPENJDK| replace:: openjdk-8-jre-headless
|
||||
.. |SRC_VERSION| replace:: 3.1
|
||||
.. |NEW_VERSION| replace:: 3.2
|
||||
.. |SCYLLA_NAME| replace:: Scylla
|
||||
.. |PKG_NAME| replace:: scylla
|
||||
.. |SCYLLA_REPO| replace:: Scylla deb repo
|
||||
.. _SCYLLA_REPO: http://www.scylladb.com/download/?platform=ubuntu-18.04
|
||||
.. |SCYLLA_METRICS| replace:: Scylla Metrics Update - Scylla 3.1 to 3.2
|
||||
.. _SCYLLA_METRICS: ../metric-update-3.1-to-3.2
|
||||
.. |SCYLLA_MONITOR| replace:: Scylla Monitoring 3.0
|
||||
.. _SCYLLA_MONITOR: /operating-scylla/monitoring/
|
||||
.. include:: /upgrade/_common/upgrade-guide-v2-ubuntu-and-debian.rst
|
||||
@@ -1,38 +0,0 @@
|
||||
=================================
|
||||
Upgrade Guide - Scylla 3.2 to 3.3
|
||||
=================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Red Hat Enterprise Linux and CentOS <upgrade-guide-from-3.2-to-3.3-rpm>
|
||||
Ubuntu 16.04 <upgrade-guide-from-3.2-to-3.3-ubuntu-16-04>
|
||||
Ubuntu 18.04 <upgrade-guide-from-3.2-to-3.3-ubuntu-18-04>
|
||||
Debian <upgrade-guide-from-3.2-to-3.3-debian>
|
||||
Metrics <metric-update-3.2-to-3.3>
|
||||
|
||||
.. raw:: html
|
||||
|
||||
|
||||
<div class="panel callout radius animated">
|
||||
<div class="row">
|
||||
<div class="medium-3 columns">
|
||||
<h5 id="getting-started">Upgrade Scylla</h5>
|
||||
</div>
|
||||
<div class="medium-9 columns">
|
||||
|
||||
Upgrade guides are available for:
|
||||
|
||||
* :doc:`Upgrade Scylla from 3.2.y to 3.3.y on Red Hat Enterprise Linux and CentOS <upgrade-guide-from-3.2-to-3.3-rpm>`
|
||||
* :doc:`Upgrade Scylla from 3.2.x to 3.3.y on Ubuntu 16.04 <upgrade-guide-from-3.2-to-3.3-ubuntu-16-04>`
|
||||
* :doc:`Upgrade Scylla from 3.2.x to 3.3.y on Ubuntu 18.04 <upgrade-guide-from-3.2-to-3.3-ubuntu-18-04>`
|
||||
* :doc:`Upgrade Scylla from 3.2.x to 3.3.y on Debian <upgrade-guide-from-3.2-to-3.3-debian>`
|
||||
* :doc:`Scylla Metrics Update - Scylla 3.2 to 3.3<metric-update-3.2-to-3.3>`
|
||||
|
||||
.. raw:: html
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -1,21 +0,0 @@
|
||||
|
||||
|
||||
Scylla Metric Update - Scylla 3.2 to 3.3
|
||||
========================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:hidden:
|
||||
|
||||
Scylla 3.3 Dashboards are available as part of the latest |mon_root|.
|
||||
|
||||
The following metrics are new in Scylla 3.3
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* scylla_cql_deletes_per_ks
|
||||
* scylla_cql_inserts_per_ks
|
||||
* scylla_cql_reads_per_ks
|
||||
* scylla_cql_select_bypass_caches
|
||||
* scylla_cql_unpaged_select_queries_per_ks
|
||||
* scylla_cql_updates_per_ks
|
||||
* scylla_reactor_abandoned_failed_futures
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user