Codership is pleased to announce a new Generally Available (GA) release of the multi-master Galera Cluster for MySQL 5.7, consisting of MySQL-wsrep 5.7.44 (release notes, download) and MySQL-wsrep 8.0.35 (release notes, download), with Galera replication library 4.17 (release notes, download) implementing wsrep API version 26. This release incorporates all changes to MySQL 5.7.44 and MySQL 8.0.35 respectively, adding a synchronous option for your MySQL High Availability solutions.
For MySQL 5.7, one should continue using the Galera replication library 3.37 implementing the wsrep API version 25 for MySQL-wsrep 5.7.32. One can presume that unless there is a bug, we will not be releasing a new version of the library, as MySQL 5.7 is End of Life (EOL) since October 2023. We strongly encourage you to upgrade from MySQL-wsrep 5.7 to MySQL-wsrep 8.0. In addition, since the EOL announcement, FreeBSD removed the expired port, so mysqlwsrep57-server is no more.
There has been a new package signing key, with key ID: 8DA84635. The old signing key is still active for older packages, but note the new signing key. This is to ensure it is compatible with Red Hat Enterprise Linux 9 and greater.
The only major changes in In MySQL 5.7.44-25.36 is the new merge with the upstream release, plus the manpages. As stated above, you are encouraged to upgrade to MySQL 8.0, as this is likely the last release in the MySQL 5.7 series. Supported operating systems are CentOS 7, RHEL 7 and 8.
In MySQL 8.0.35-26.16, during the joiner CLONE SST process, a temporary user was created and dropped, and this is added to the binary log by default and sets off the MySQL GTID. This is now fixed, as the joiner process operations are now disabled from binlogging. In addition, when it comes to SST user account management, there is automatic creation of temporary accounts for SST, passed via socket (and not environment variables). Account credentials can be passed directly to the SST script. This is more secure, and also helps with simple node configuration. It should also be noted that wsrep_sst_auth set by the administrator is also respected. It works for mysqldump, CLONE, and xtrabackup methods.
When using wsrep_notify_cmd, the script is now only called when Galera Cluster has formed a cluster view or when it is synced or is the donor, and this ensures that it prevents any untoward hangs. It should be noted that INFORMATION_SCHEMA.PROCESSLISTis now deprecated, and one should use PERFORMANCE_SCHEMA.PROCESSLIST instead. One can find information on appliers and rollback threads via SELECT * FROM PERFORMANCE_SCHEMA WHERE NAME = 'thread/sql/wsrep_applier_thread'; or SELECT * FROM PERFORMANCE_SCHEMA WHERE NAME = 'thread/sql/wsrep_rollback_thread';.
There is now a new foreign key constraint check retrying implementation, as we have found on occasion, foreign key constrains may fail even though the constraints themselves are not violated (e.g. the same transaction inserts in the parent table, and the next insert into the child table fails in FK checks). The number of retries by default is set to 1, and can be controlled by the new system variable wsrep_applier_FK_failure_retries. If the constraint check fails despite retires, the final retry prints out a warning with an error code and InnoDB system monitor output for further troubleshooting.
For MySQL 8.0.35, we build packages for many operating systems: Debian 10 and 11, Ubuntu 20.04 and 22.04, CentOS 7, and Red Hat Enterprise Linux 7, 8 and 9.
Please download the latest software and update your Galera Clusters! We continue to provide repositories for popular Linux distributions, and we encourage you to use them. Contact us more more information about what Galera Cluster Enterprise Edition can do for you.