Upgrade Multi-Node MariaDB ColumnStore from 6 to 23.10
Upgrade a multi-node MariaDB ColumnStore cluster from 6 to 23.10, with MaxScale-based replica maintenance mode, controlled service stops, and per-node upgrade steps.
These instructions detail the upgrade from MariaDB ColumnStore 6 to MariaDB ColumnStore 23.10 in a Multi-Node topology on a range of supported Operating Systems.
Set Replicas to Maintenance Mode
This action is performed for each replica server on the MaxScale node.
Prior to upgrading, the replica servers must be set to maintenance mode in MaxScale. The replicas can be set to maintenance mode in MaxScale using . If you are using , the replicas can be set to maintenance mode using the set server command:
maxctrl set server \
mcs2 \
maintenance
As the first argument, provide the name for the server
As the second argument, provide maintenance as the state
Confirm Maintenance Mode is Set for Replicas
This action is performed on the MaxScale node.
Confirm that the replicas are set to maintenance mode in MaxScale using MaxScale's REST API. If you are using MaxCtrl, the state of the replicas can be viewed using the list servers command:
If the node is properly in maintenance mode, then the State column will show Maintenance as one of the states.
Disable GTID Strict Mode
This action is performed on each replica server.
The system variable must be disabled for this upgrade procedure. If the gtid_strict_mode system variable is enabled in any configuration files, disable it temporarily until the upgrade procedure is complete.
You can check if the gtid_strict_mode system variable is set in a configuration file by executing my_print_defaults command with the mysqld option:
If the gtid_strict_mode system variable is set, you can temporarily disable it by adding # in front of it in the configuration file, so that it will be treated as a comment and ignored:
[mariadb]
...
# temporarily commented out for upgrade
# gtid_strict_mode=1
Shutdown ColumnStore
Prior to upgrading, MariaDB Enterprise ColumnStore must be shutdown.
mcs cluster stop
Stop Services
This action is performed on each ColumnStore node.
Prior to upgrading, several services must be stopped on each ColumnStore node:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies:
Enterprise ColumnStore 23.10 is included with MariaDB Enterprise Server 11.4. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup.
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies.
The update command depends on the installed APT version, which can be determined by executing the following command:
apt --version
apt 2.0.9 (amd64)
For versions prior to APT 2.0, execute the following command:
sudo apt install --only-upgrade "mariadb*"
For APT 2.0 and later, execute the following command:
CMAPI disables the Enterprise ColumnStore service in a multi-node deployment. The Enterprise ColumnStore service will be started as-needed by the CMAPI service, so it does not need to start automatically upon reboot.
Start Services
This action is performed on each ColumnStore node.
After upgrading, the CMAPI service and the MariaDB Enterprise Server service must be started on each ColumnStore node:
Start the CMAPI service:
sudo systemctl start mariadb-columnstore-cmapi
Start the MariaDB Enterprise Server service:
sudo systemctl start mariadb
Write Binary Log
On the primary server, run mariadb-upgrade to upgrade the data directory with binary logging enabled to update the system tables:
mariadb-upgrade --write-binlog
Start ColumnStore
After upgrading, MariaDB Enterprise ColumnStore must be started.
mcs cluster start
Enable GTID Strict Mode
This action is performed on each replica server.
If you temporarily disabled the system variable in the Disable GTID Strict Mode step, it can be re-enabled. If the gtid_strict_mode system variable was temporarily disabled in any configuration files, re-enable it.
Confirm ColumnStore Version
This action is performed on each ColumnStore node.
After upgrading, it is recommended to confirm the Enterprise ColumnStore version on each ColumnStore node. Connect to the node using and query the ColumnStore_version status variable with :
This action is performed on each ColumnStore node.
After upgrading, it is recommended to confirm the ES version on each ColumnStore node. Connect to the node using and query the system variable with :
SHOW GLOBAL VARIABLES LIKE 'version';
+---------------+----------------------------------+
| Variable_name | Value |
+---------------+----------------------------------+
| version | 10.6.9-5-MariaDB-enterprise-log |
+---------------+----------------------------------+
Clear Maintenance Mode for Replicas
This action is performed for each replica server on the MaxScale node.
After the upgrade, maintenance mode for each replica has been cleared in MaxScale using . If you are using , maintenance mode can be cleared using the clear server command:
maxctrl clear server \
mcs2 \
maintenance
As the first argument, provide the name for the server
As the second argument, provide maintenance as the state
Confirm Maintenance Mode is Cleared for Replicas
This action is performed for each replica server on the MaxScale node.
Confirm that maintenance mode in MaxScale has been cleared for each replica using . If you are using , the state of the replicas can be viewed using the list servers command: