The Ultimate Guide to High Availability with MariaDB

Is it possible to downgrade a Galera clusternode to a slightly older version and rejoin the cluster?

I'm trying to troubleshoot a situation that occurred after recent upgrade of all three nodes from MariaDB 10.2.19 to 10.2.18. Is it possiblt to take one node, uninstall MariaDB 10.2.18 and (somehow?) install 10.2.9 and then make it rejoin the cluster even if the other two nodes are still the newest version 10.2.18, and the joiner is 10.2.9.

All this just to see if the problem will disappear on the older version 10.2.9

Or - would it be required to downgrade all nodes with mysqldump/import?

Thanks in advance for any suggestions/answers!

Answer Answered by Geoff Montee in this comment.

That should be fine, as long as there were no changes between MariaDB 10.2.9 and MariaDB 10.2.18 that broke backward compatibility. I took a quick look through the release notes for all of the releases between those versions, and I didn't see any.

However, I believe that MariaDB 10.2.19 did introduce a backward incompatible change with the new redo log changes that are tied to innodb_safe_truncate. It sounds like you aren't actually using MariaDB 10.2.19 though.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.