Performing a Rolling Upgrade

The following steps can be used to perform a rolling upgrade from MariaDB Galera Cluster 5.5 to MariaDB Galera Cluster 10.0. In a rolling upgrade, each node is upgraded individually, so the cluster is always operational. There is no downtime from the application's perspective.

First, before you get started:

1. First, take a look at Upgrading from MariaDB 5.5 to MariaDB 10.0 to see what has changed between the major versions.
   1. Check whether any system variables or options have been changed or removed. Make sure that your server's configuration is compatible with the new MariaDB version before upgrading.
   2. Check whether replication has changed in the new MariaDB version in any way that could cause issues while the cluster contains upgraded and non-upgraded nodes.
   3. Check whether any new features have been added to the new MariaDB version. If a new feature in the new MariaDB version cannot be replicated to the old MariaDB version, then do not use that feature until all cluster nodes have been upgrades to the new MariaDB version.
2. Next, make sure that the Galera version numbers are compatible.
   1. If you are upgrading from the most recent MariaDB Galera Cluster 5.5 release to MariaDB Galera Cluster 10.0, then the versions will be compatible. The latest releases of MariaDB Galera Cluster 5.5 and MariaDB Galera Cluster 10.0 use Galera 3 (i.e. Galera wsrep provider versions 25.3.x), so they should be compatible.
   2. If you are running an older MariaDB Galera Cluster 5.5 release that still uses Galera 2 (i.e. Galera wsrep provider versions 25.2.x), then it is recommended to first upgrade to the latest MariaDB Galera Cluster 5.5 release that uses Galera 3 (i.e. Galera wsrep provider versions 25.3.x).
   3. See What is MariaDB Galera Cluster?: Galera wsrep provider Versions for information on which MariaDB releases uses which Galera wsrep provider versions.
3. Ideally, you want to have a large enough gcache to avoid a State Snapshot Transfer (SST) during the rolling upgrade. The gcache size can be configured by setting gcache.size For example:
   wsrep_provider_options="gcache.size=2G"

Then, for each node, perform the following steps:

1. Modify the repository configuration, so the system's package manager installs MariaDB 10.1. For example,
   • On Debian, Ubuntu, and other similar Linux distributions, see Updating the MariaDB APT repository to a New Major Release for more information.
   • On RHEL, CentOS, Fedora, and other similar Linux distributions, see Updating the MariaDB YUM repository to a New Major Release for more information.
   • On SLES, OpenSUSE, and other similar Linux distributions, see Updating the MariaDB ZYpp repository to a New Major Release for more information.
2. If you use a load balancing proxy such as MaxScale or HAProxy, make sure to drain the server from the pool so it does not receive any new connections.
3. Set innodb_fast_shutdown to 0. It can be changed dynamically with SET GLOBAL. For example:
   SET GLOBAL innodb_fast_shutdown=0;
4. Stop MariaDB.
5. Uninstall the old version of MariaDB and the Galera wsrep provider.
   • On Debian, Ubuntu, and other similar Linux distributions, execute the following:
     sudo apt-get remove mariadb-galera-server galera
   • On RHEL, CentOS, Fedora, and other similar Linux distributions, execute the following:
     sudo yum remove MariaDB-Galera-server galera
   • On SLES, OpenSUSE, and other similar Linux distributions, execute the following:
     sudo zypper remove MariaDB-Galera-server galera
6. Install the new version of MariaDB and the Galera wsrep provider.
   • On Debian, Ubuntu, and other similar Linux distributions, see Installing MariaDB Packages with APT for more information.
   • On RHEL, CentOS, Fedora, and other similar Linux distributions, see Installing MariaDB Packages with YUM for more information.
   • On SLES, OpenSUSE, and other similar Linux distributions, see Installing MariaDB Packages with ZYpp for more information.
7. Make any desired changes to configuration options in option files, such as my.cnf. This includes removing any system variables or options that are no longer supported.
8. Start MariaDB.
9. Run mysql_upgrade with the --skip-write-binlog option.
   • mysql_upgrade does two things:
     1. Ensures that the system tables in the mysql database are fully compatible with the new version.
     2. Does a very quick check of all tables and marks them as compatible with the new version of MariaDB .

When this process is done for one node, move onto the next node.

: