Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Critical
-
Resolution: Unresolved
-
10.6.17, 10.6.18
-
None
Description
Whenever we upgrade Galera to the newer version in the minor MariaDB x.y.z release, we should explicitly mention this in the release notes. For 10.6.18, for example, this had NOT happened:
https://mariadb.com/kb/en/mariadb-10-6-18-release-notes/
Moreover, some new minor Galera versions introduce protocol changes and bump protocols versions, like it happened with 26.4.18:
https://releases.galeracluster.com/galera-4.18/release-notes-galera-26.4.18.txt
We should carefully check that and document as a notable change, as it prevents downgrading individual nodes in the cluster to older versions with messages like these:
2024-07-23 12:17:29 0 [ERROR] WSREP: /home/jenkins/workspace/Galera/Build-Galera-Package/galera-src/gcs/src/gcs_group.cpp:group_check_proto_ver():341: Group requested gcs_proto_ver: 3, max supported by this node: 2.Upgrade the node before joining this group.Need to abort.
|
2024-07-23 12:17:29 0 [ERROR] WSREP: /home/jenkins/workspace/Galera/Build-Galera-Package/galera-src/gcs/src/gcs_group.cpp:group_check_proto_ver():342: Group requested repl_proto_ver: 11, max supported by this node: 10.Upgrade the node before joining this group.Need to abort.
|
and are usually not expected for different minor releases.