From be6c3022ce9b381bd334cc079aed544ef0d44fc6 Mon Sep 17 00:00:00 2001 From: Anna Stuchlik Date: Fri, 17 Mar 2023 11:57:58 +0100 Subject: [PATCH] doc: fix the service name in upgrade guides Fixes https://github.com/scylladb/scylladb/issues/13207 This commit fixes the service and package names in the upgrade guides 5.0-to-2022.1 and 5.1-to-2022.2. Service name: scylla-server Package name: scylla-enterprise Previous PRs to fix the same issue in other upgrade guides: https://github.com/scylladb/scylladb/pull/12679 https://github.com/scylladb/scylladb/pull/12698 This commit must be backported to branch-5.1 and branch 5.2. Closes #13225 (cherry picked from commit 922f6ba3dd30a3856ca18190a3fd66c8765efa38) --- ...rade-guide-from-5.0-to-2022.1-ubuntu-and-debian.rst | 4 ++-- .../upgrade-guide-from-5.0-to-2022.1-rpm.rst | 2 +- .../upgrade-guide-from-5.1-to-2022.2-generic.rst | 10 +++++----- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/upgrade/_common/upgrade-guide-from-5.0-to-2022.1-ubuntu-and-debian.rst b/docs/upgrade/_common/upgrade-guide-from-5.0-to-2022.1-ubuntu-and-debian.rst index 7b28fe635f..1b7f3a2650 100644 --- a/docs/upgrade/_common/upgrade-guide-from-5.0-to-2022.1-ubuntu-and-debian.rst +++ b/docs/upgrade/_common/upgrade-guide-from-5.0-to-2022.1-ubuntu-and-debian.rst @@ -114,7 +114,7 @@ New io.conf format was introduced in ScyllaDB 2.3 and 2019.1. If your io.conf do .. code:: sh - sudo service scylla-enterprise-server start + sudo service scylla-server start Validate -------- @@ -154,7 +154,7 @@ Gracefully shutdown ScyllaDB .. code:: sh nodetool drain - sudo service scylla-enterprise-server stop + sudo service scylla-server stop Download and install the old release ------------------------------------ diff --git a/docs/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.0-to-2022.1/upgrade-guide-from-5.0-to-2022.1-rpm.rst b/docs/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.0-to-2022.1/upgrade-guide-from-5.0-to-2022.1-rpm.rst index 500f194b81..d32905866f 100644 --- a/docs/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.0-to-2022.1/upgrade-guide-from-5.0-to-2022.1-rpm.rst +++ b/docs/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.0-to-2022.1/upgrade-guide-from-5.0-to-2022.1-rpm.rst @@ -109,7 +109,7 @@ A new io.conf format was introduced in ScyllaDB 2.3 and 2019.1. If your io.conf .. code:: sh - sudo systemctl start scylla-enterprise-server + sudo systemctl start scylla-server Validate -------- diff --git a/docs/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.1-to-2022.2/upgrade-guide-from-5.1-to-2022.2-generic.rst b/docs/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.1-to-2022.2/upgrade-guide-from-5.1-to-2022.2-generic.rst index 337c066ede..725f19a38d 100644 --- a/docs/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.1-to-2022.2/upgrade-guide-from-5.1-to-2022.2-generic.rst +++ b/docs/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.1-to-2022.2/upgrade-guide-from-5.1-to-2022.2-generic.rst @@ -144,7 +144,7 @@ Download and install the new release sudo apt-get clean all sudo apt-get update sudo apt-get remove scylla\* - sudo apt-get install scylla-enterprise-server + sudo apt-get install scylla-enterprise sudo systemctl daemon-reload Answer ‘y’ to the first two questions. @@ -163,7 +163,7 @@ Download and install the new release sudo yum clean all sudo rm -rf /var/cache/yum sudo yum remove scylla\* - sudo yum install scylla-enterprise-server + sudo yum install scylla-enterprise .. group-tab:: EC2/GCP/Azure Ubuntu Image @@ -221,13 +221,13 @@ Start the node .. code:: sh - sudo service scylla-enterprise-server start + sudo service scylla-server start Validate -------- #. Check cluster status with ``nodetool status`` and make sure **all** nodes, including the one you just upgraded, are in ``UN`` status. #. Use ``curl -X GET "http://localhost:10000/storage_service/scylla_release_version"`` to check the ScyllaDB version. Validate that the version matches the one you upgraded to. -#. Check scylla-enterprise-server log (using ``journalctl _COMM=scylla``) and ``/var/log/syslog`` to validate there are no new errors in the log. +#. Check scylla-server log (using ``journalctl _COMM=scylla``) and ``/var/log/syslog`` to validate there are no new errors in the log. #. Check again after two minutes, to validate no new issues are introduced. Once you are sure the node upgrade was successful, move to the next node in the cluster. @@ -269,7 +269,7 @@ Drain and gracefully stop the node .. code:: sh nodetool drain - sudo service scylla-enterprise-server stop + sudo service scylla-server stop Download and install the old release ------------------------------------