Comments - Upgrading Between Minor Versions with Galera Cluster
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.
However, this can cause issues if you restart a non-upgraded node in a cluster where the rest of the nodes have been upgraded.
What is meant by upgrading the rest of the nodes? Doesn't upgrading a node require restarting?
When exactly do nodes (or the whole cluster) switch to the new wsrep protocol version? When all known nodes of a cluster have upgraded the wsrep provider? Or when all nodes that are online have upgraded the wsrep provider? Or sth else?
Thanks!
/fn
Can anybody explain why mysql_upgrade/mariadb-upgrade should be called with the option --skip-write-binlog?
The default is write_binlog = false anyway:
mariadb-upgrade --help | grep ^write-binlog write-binlog FALSE
Have you found any answer regarding your question? On a Debian machines there is startup-script (/etc/mysql/debian-start) which runs mysql_upgrade on each start. I was just wondering, if I should remove this script (and run it manually) or add the --skip-write-brinlog to it.... (it's a galera cluster)