This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.

Updating MariaDB with Galera
Prev Chapter 1. Maintenance Next

Updating MariaDB with Galera

Updating MariaDB with Galera must be done manually. Crowbar does not install updates automatically. Updates can be done with Pacemaker or with the CLI. In particular, manual updating applies to upgrades to MariaDB 10.2.17 or higher from MariaDB 10.2.16 or earlier. See MariaDB 10.2.22 Release Notes - Notable Changes.

Note

In order to run the following update steps, the database cluster needs to be up and healthy.

Using the Pacemaker GUI, update MariaDB with the following procedure:

  1. Put the cluster into maintenance mode. Detailed information about the Pacemaker GUI and its operation is available in the https://documentation.suse.com/sle-ha/15-SP1/single-html/SLE-HA-guide/#cha-conf-hawk2.

  2. Perform a rolling upgrade to MariaDB following the instructions at Upgrading Between Minor Versions with Galera Cluster.

    The process involves the following steps:

    1. Stop MariaDB

    2. Uninstall the old versions of MariaDB and the Galera wsrep provider

    3. Install the new versions of MariaDB and the Galera wsrep provider

    4. Change configuration options if necessary

    5. Start MariaDB

    6. Run mysql_upgrade with the --skip-write-binlog option

  3. Each node must upgraded individually so that the cluster is always operational.

  4. Using the Pacemaker GUI, take the cluster out of maintenance mode.

When updating with the CLI, the database cluster must be up and healthy. Update MariaDB with the following procedure:

  1. Mark Galera as unmanaged: 

    crm resource unmanage galera

    Or put the whole cluster into maintenance mode: 

    crm configure property maintenance-mode=true

  2. Pick a node other than the one currently targeted by the load balancer and stop MariaDB on that node: 

    crm_resource --wait --force-demote -r galera -V

  3. Perform updates with the following steps:

    1. Uninstall the old versions of MariaDB and the Galera wsrep provider.

    2. Install the new versions of MariaDB and the Galera wsrep provider. Select the appropriate instructions at Installing MariaDB with zypper.

    3. Change configuration options if necessary.

  4. Start MariaDB on the node. 

    crm_resource --wait --force-promote -r galera -V

  5. Run mysql_upgrade with the --skip-write-binlog option.

  6. On the other nodes, repeat the process detailed above: stop MariaDB, perform updates, start MariaDB, run mysql_upgrade.

  7. Mark Galera as managed: 

    crm resource manage galera

    Or take the cluster out of maintenance mode.

Prev Up Next
Bootstrapping the MariaDB Galera Cluster with Pacemaker when a node is missing Home Load Balancer: Octavia Administration