[MDEV-28483] Include the details about 10.4 to 10.5 and newer major versions upgrades for Galera clusters into the Knowledge Base Created: 2022-05-06  Updated: 2024-02-06

Status: In Progress
Project: MariaDB Server
Component/s: Documentation - Codership, Galera
Fix Version/s: N/A

Type: Task Priority: Critical
Reporter: Valerii Kravchuk Assignee: Rahul
Resolution: Unresolved Votes: 4
Labels: documentation, galera, kb

Issue Links:
PartOf
Relates
relates to MDEV-31332 Galera SST rsync wants to replicate s... Closed
relates to MDEV-31506 Updating cluster to a new major versi... Confirmed
relates to MDEV-31536 Galera mariadb-backup to work as SST ... Open
relates to MDEV-29162 Major upgrade instructions missing fo... Closed

 Description   

In https://mariadb.com/kb/en/upgrading-galera-cluster/ we see that major version upgrade instructions end up with 10.3 to 10.4 upgrade:

https://mariadb.com/kb/en/upgrading-from-mariadb-103-to-mariadb-104-with-galera-cluster/

We need similar detailed steps for the following upgrades:

  • 10.4 to 10.5,
  • 10.5 to 10.6,
    Any effort beyond that should be a decision taken by Codership (janlindstrom FYI)

Maybe in a single document if there is no real difference (but I assume some details may still differ for an upgrade from 10.5 to 10.6, for example). Then, we need a page added for each major release before it is declared GA.

Status update
2023 12 20 - rahulmalik from Codership is currently testing before we can document.
2023 12 31 - The important scope has been clarified with ralf.gebhardt.
2024 01 10 - MDEV-29162 is fixed

 Comments   
Comment by Daniel Black [ 2022-05-18 ]

Note MDEV-27437 and https://mariadb.com/kb/en/introduction-to-state-snapshot-transfers-ssts/#rsync-rsync_wan that includes explicit sst=rsync and innodb_aio=0 requirements.

Comment by COUNOTTE CEDRIC [ 2022-07-12 ]

Is there a documentation to migrate a slave server from 10.5 to 10.6 ?

I'm using the method at this URL to setup/start replication: https://mariadb.com/kb/en/configuring-mariadb-replication-between-two-mariadb-galera-clusters/

So far I read SST using mariabackup is not compatible with major version upgrades, however I just upgraded a 2 node galera cluster from 10.5 to 10.6, the first node did a SST and successfully sync'ed with first which is a slave of another busy cluster.

That said one need to use 10.6.8 at least to avoid MDEV-28946 which then prevents SST from completing.

Comment by Daniel Bray [ 2023-05-24 ]

Just ran across this and noticed the documentation was indeed not there. It would be great to have this, as the upgrade is failing for me, and I have no documentation to reference. Using the original process, I went from 10.5 -> 10.6 just fine, and then from 10.6 -> 10.7 as well. However, the 10.7 ->10.8 is failing with:
[ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.10. You must start up and shut down MariaDB 10.7 or earlier.

Comment by Daniel Black [ 2023-11-29 ]

dbray_sd, sorry your error, depending on SST mechanism, is either MDEV-27437 or MDEV-31536. mysqldump might be the only way isn't broken.

I was working on this a few months ago but ran out of time - https://github.com/grooverdan/mariadb.org-tools/blob/galera_major_version_upgrade-MDEV-31536-MDEV-31506/daniel/galera-sst-test

For testing container privileged mode to start fuse connections but a bit of scripting is needed to finish off all netcat implementations consistently and ideally wrapping up the common sshfs aspects between rsync/mariadbbackup so its maintainable.

Comment by Ian Gilfillan [ 2024-01-15 ]

rahulmalik the above is a little ambiguous to me. Can you confirm that you succeeded with 10.4 to 11.4 with the initial steps, and only failed when trying to enforce SST? In which case the docs should be as before with addition of a note to avoid SST.

Comment by Rahul [ 2024-02-06 ]

greenman looks good to me.

Generated at Thu Feb 08 10:01:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.