Scylla Documentation Logo Documentation
  • Server
    • Scylla Open Source
    • Scylla Enterprise
    • Scylla Alternator
  • Cloud
    • Scylla Cloud
    • Scylla Cloud Docs
  • Tools
    • Scylla Manager
    • Scylla Monitoring Stack
    • Scylla Operator
  • Drivers
    • CQL Drivers
    • DynamoDB Drivers
Download
Menu
Scylla Scylla for Administrators Scylla Manager Upgrade Scylla Manager Upgrade Scylla Manager 1.2 to 1.3 Upgrade Guide - Scylla Manager 1.2.x to 1.3.x on CentOS

Upgrade Guide - Scylla Manager 1.2.x to 1.3.x on CentOS¶

Enterprise customers who use Scylla Manager 1.2.x are encouraged to upgrade to 1.3.x. For new installations please see Scylla Manager - Download and Install. The steps below instruct you how to upgrade the Scylla Manager server while keeping the manager datastore intact. If you are not running Scylla Manager 1.2.x, do not perform this upgrade procedure. This procedure only covers upgrades from Scylla Manager 1.2.x to 1.3.x.

Please contact Scylla Enterprise Support team with any questions.

Upgrade Notes¶

  • This upgrade brings to sctool a new command: status. This command shows a listing of the individual nodes in the cluster and records the CQL availability on the nodes.

  • Health Check - This upgrade introduces a new feature where each node is monitored by Scylla Manager. When Scylla Manager detects that a node is down an alert message is sent to Scylla Monitoring. Alternitively, you can use the sctool status` command to show the live cluster status.

  • Automated health check - When a cluster is added a new health check task is automatically added to the cluster. Following an upgrade, all existing clusters will have an health check task as well.

  • The sctool argument interval-days has been renamed to interval as it now supports more granular time units. For example: 3d2h10m. The available time units are d, h, m, and s.

  • The sctool command cluster list no longer displays the host column in the results table. This was removed because it was easy to be mislead that this node was the only node being used. Adding a cluster (cluster add) still takes a --host argument, but when all the available nodes are discovered they are persisted and used for subsequent interactions with ScyllaDB.

Upgrade Procedure¶

  • Backup the data

  • Download and install new packages

  • Validate that the upgrade was successful

Backup the Scylla Manager data¶

Scylla Manager server persists its data to a Scylla cluster (data store). Before upgrading, backup the scylla_manager keyspace from Scylla Manager’s backend, following this backup procedure.

Download and install the new release¶

Before upgrading, check what version you are currently running now using rpm -q scylla-manager. You should use the same version that you had previously installed in case you want to rollback the upgrade.

To upgrade:

  1. Update the Update the Scylla Manager repo: to 1.3.x

  2. Run:

sudo yum update scylla-manager -y
  1. Reload your shell execute the below command to reload sctool code completion.

source /etc/bash_completion.d/sctool.bash

Validate¶

  1. Check that Scylla Manager service is running with sudo systemctl status scylla-manager.service. Confirm the service is active (running). If not, then start it with systemctl start scylla-manager.service.

  2. Confirm that the upgrade changed the Client and Server version. Run sctool version and make sure both are 1.3.x version. For example:

sctool version
Client version: 1.3.0-0.20181130.03ae248
Server version: 1.3.0-0.20181130.03ae248
  1. Confirm that following the update, that your managed clusters are still present. Run sctool cluster list

sctool cluster list
╭──────────────────────────────────────┬──────────┬───────────────╮
│ cluster id                           │ name     │ssh user       │
├──────────────────────────────────────┼──────────┼───────────────┤
│ db7faf98-7cc4-4a08-b707-2bc59d65551e │ cluster  │scylla-manager │
╰──────────────────────────────────────┴──────────┴───────────────╯
  1. Confirm that following the upgrade, there is a healtcheck task for each existing cluster. Run sctool task list to list the tasks.

sctool task list -c cluster --all
╭──────────────────────────────────────────────────┬───────────────────────────────┬──────┬────────────┬────────╮
│ task                                             │ next run                      │ ret. │ properties │ status │
├──────────────────────────────────────────────────┼───────────────────────────────┼──────┼────────────┼────────┤
│ healthcheck/afe9a610-e4c7-4d05-860e-5a0ddf14d7aa │ 10 Dec 18 20:21 UTC (+15s)    │ 0    │            │ RUNNING│
│ repair/4d79ee63-7721-4105-8c6a-5b98c65c3e21      │ 12 Dec 18 00:00 UTC (+7d)     │ 3    │            │ NEW    │
╰──────────────────────────────────────────────────┴───────────────────────────────┴──────┴────────────┴────────╯

Rollback Procedure¶

The following procedure describes a rollback from Scylla Manager 1.3 to 1.2. Apply this procedure if an upgrade from 1.2 to 1.3 failed for any reason.

Warning: note that you may lose the manged clusters after downgrade. Should this happen, you will need to add the managed clusters clusters manually.

  • Downgrade to previous release

  • Start Scylla Manager

  • Valdate Scylla Manager version

Downgrade to previous release¶

  1. Stop Scylla Manager

sudo systemctl stop scylla-manager
  1. Drop the scylla_manager keyspace from the remote datastore

cqlsh -e "DROP KEYSPACE scylla_manager"
  1. Remove Scylla Manager repo

sudo rm -rf /etc/yum.repos.d/scylla-manager.repo
sudo yum clean all
sudo rm -rf /var/cache/yum
  1. Update the Scylla Manager repo to 1.2.x

  2. Install previous version

sudo yum downgrade scylla-manager scylla-manager-server scylla-manager-client -y

Rollback the Scylla Manager database¶

  1. Start Scylla Manager to reinitialize the data base schema.

sudo systemctl start scylla-manager
  1. Stop Scylla Manager to avoid issues while restoring the backup. If you did not perform any backup before upgrading then you are done now and can continue at “Start Scylla Manager”.

sudo systemctl stop scylla-manager
  1. Restore the database backup if you performed a backup by following the instructions in Restore from a Backup. You can skip step 1 since the Scylla Manager has done this for you.

Start Scylla Manager¶

sudo systemctl start scylla-manager

Validate Scylla Manager Version¶

Validate Scylla Manager version:

sctool version

The version should match with the results you had previously.

PREVIOUS
Upgrade Scylla Manager 1.2 to 1.3
NEXT
upgrade guide - Scylla Manager 1.2.x to 1.3.x on Ubuntu 16
  • Getting Started
    • Install Scylla
      • Scylla Unified Installer (relocatable executable)
      • Air-gapped Server Installation
      • What is in each RPM
      • Scylla Housekeeping and how to disable it
      • Scylla Developer Mode
      • Scylla Configuration Reference
    • Configure Scylla
    • Scylla Requirements
      • System Requirements
      • OS Support by Platform and Version
      • Scylla in a Shared Environment
    • Cassandra Query Language (CQL)
      • CQLSh the CQL shell
      • Data Definition
      • Data Manipulation
      • Expiring Data with Time to Live (TTL)
      • Additional Information
      • Security
      • Data Types
      • Appendices
      • Definitions
      • Materialized Views
      • Functions
      • JSON
      • Global Secondary Indexes
      • Additional Information
      • Compaction
      • Consistency Levels
      • Reserved Keywords
      • Non-reserved Keywords
    • CQLSh: the CQL shell
    • Scylla Drivers
      • Scylla CQL Drivers
      • Scylla DynamoDB Drivers
    • Migrate to Scylla
      • Migration Process from Cassandra to Scylla
      • Scylla and Apache Cassandra Compatibility
      • Migration Tools Overview
    • Integration Solutions
      • Integrate Scylla with Spark
      • Integrate Scylla with KairosDB
      • Integrate Scylla with Presto
      • Integrate Scylla with Elasticsearch
      • Integrate Scylla with Kubernetes
      • Integrate Scylla with the JanusGraph Graph Data System
      • Integrate Scylla with DataDog
      • Integrate Scylla with Kafka
      • Integrate Scylla with IOTA Chronicle
      • Integrate Scylla with Spring
      • Shard-Aware Kafka Connector for Scylla
      • Install Scylla with Ansible
      • Integrate Scylla with Databricks
    • Tutorials
  • Scylla for Administrators
    • Administration Guide
    • Procedures
      • Cluster Management
      • Backup & Restore
      • Change Configuration
      • Maintenance
      • Best Practices
      • Benchmarking Scylla
      • Migrate from Cassandra to Scylla
      • Disable Housekeeping
    • Security
      • Scylla Security Checklist
      • Enable Authentication
      • Enable and Disable Authentication Without Downtime
      • Generate a cqlshrc File
      • Reset Authenticator Password
      • Enable Authorization
      • Grant Authorization CQL Reference
      • Role Based Access Control (RBAC)
      • Scylla Auditing Guide
      • Encryption: Data in Transit Client to Node
      • Encryption: Data in Transit Node to Node
      • Generating a self-signed Certificate Chain Using openssl
      • Encryption at Rest
      • LDAP Authentication
      • LDAP Authorization (Role Management)
    • Admin Tools
      • Nodetool Reference
      • CQLSh
      • REST
      • Tracing
      • scylla-sstable
      • SSTableLoader
      • cassandra-stress
      • SSTabledump
      • SSTable2json
      • SSTable Index
      • Scylla Logs
      • Seastar Perftune
    • Scylla Manager
      • Scylla Manager Docs
      • Upgrade Scylla Manager
      • Monitoring Support Matrix
    • Scylla Monitoring Stack
      • Latest Version
      • Upgrade Scylla Monitoring Stack
      • Monitoring Support Matrix
    • Scylla Operator
    • Upgrade Procedures
      • Scylla Enterprise
      • Scylla Open Source
      • Scylla Open Source to Scylla Enterprise
      • Scylla Manager
      • Scylla Monitoring
      • Scylla AMI
    • System Configuration
      • System Configuration Guide
      • scylla.yaml
      • Scylla Snitches
    • Benchmarking Scylla
  • Scylla for Developers
    • Learn To Use Scylla
      • Scylla University
      • Course catalog
      • Scylla Essentials
      • Basic Data Modeling
      • Advanced Data Modeling
      • MMS - Learn by Example
      • Care-Pet an IoT Use Case and Example
    • CQLSh
    • Apache Cassandra Query Language (CQL)
    • Scylla Alternator
    • Scylla Features
      • Scylla Open Source Features
      • Scylla Enterprise Features
    • Scylla Drivers
      • Scylla CQL Drivers
      • Scylla DynamoDB Drivers
  • Scylla Architecture
    • Scylla Ring Architecture
    • Scylla Fault Tolerance
    • Consistency Level Console Demo
    • Scylla Anti-Entropy
      • Scylla Hinted Handoff
      • Scylla Read Repair
      • Scylla Repair
    • SSTable
      • Scylla SSTable - 2.x
      • Scylla SSTable - 3.x
    • Compaction Strategies
  • Troubleshooting Scylla
    • Errors and Support
      • Report a Scylla problem
      • Error Messages
      • Change Log Level
    • Scylla Startup
      • Ownership Problems
      • Scylla will not Start
      • Scylla Python Script broken
    • Cluster and Node
      • Failed Decommission Problem
      • Cluster Timeouts
      • Node Joined With No Data
      • SocketTimeoutException
      • NullPointerException
    • Data Modeling
      • Scylla Large Partitions Table
      • Scylla Large Rows and Cells Table
      • Large Partitions Hunting
    • Data Storage and SSTables
      • Space Utilization Increasing
      • Disk Space is not Reclaimed
      • SSTable Corruption Problem
      • Pointless Compactions
      • Limiting Compaction
    • CQL
      • Time Range Query Fails
      • COPY FROM Fails
      • CQL Connection Table
      • Reverse queries fail
    • Scylla Monitor and Manager
      • Manager and Monitoring integration
      • Manager lists healthy nodes as down
  • Knowledge Base
    • Upgrading from experimental CDC
    • Compaction
    • Counting all rows in a table is slow
    • CQL Query Does Not Display Entire Result Set
    • When CQLSh query returns partial results with followed by “More”
    • Run Scylla and supporting services as a custom user:group
    • Decoding Stack Traces
    • Snapshots and Disk Utilization
    • DPDK mode
    • Debug your database with Flame Graphs
    • How to Change gc_grace_seconds for a Table
    • Gossip in Scylla
    • Increase Permission Cache to Avoid Non-paged Queries
    • How does Scylla LWT Differ from Apache Cassandra ?
    • Map CPUs to Scylla Shards
    • Scylla Memory Usage
    • NTP Configuration for Scylla
    • POSIX networking for Scylla
    • Scylla consistency quiz for administrators
    • Recreate RAID devices
    • How to Safely Increase the Replication Factor
    • Scylla and Spark integration
    • Increase Scylla resource limits over systemd
    • Scylla Seed Nodes
    • How to Set up a Swap Space
    • Scylla Snapshots
    • Stopping a local repair
    • System Limits
    • How to flush old tombstones from a table
    • Time to Live (TTL) and Compaction
    • Scylla Nodes are Unresponsive
    • Update a Primary Key
    • Using the perf utility with Scylla
    • Configure Scylla Networking with Multiple NIC/IP Combinations
  • Scylla University
  • Scylla FAQ
  • Contribute to Scylla
  • Glossary
  • Create an issue

On this page

  • Upgrade Guide - Scylla Manager 1.2.x to 1.3.x on CentOS
    • Upgrade Notes
    • Upgrade Procedure
      • Backup the Scylla Manager data
      • Download and install the new release
      • Validate
    • Rollback Procedure
      • Downgrade to previous release
      • Rollback the Scylla Manager database
      • Start Scylla Manager
      • Validate Scylla Manager Version
Logo
Docs Contact Us About Us
Mail List Icon Slack Icon
© 2022, ScyllaDB. All rights reserved.
Last updated on 10 May 2022.
Powered by Sphinx 4.3.2 & ScyllaDB Theme 1.2.1