MySQL Cluster Manager 8.3 Release Notes  /  Changes in MySQL Cluster Manager 8.3.0 (2024-01-16, Innovation Release)

Changes in MySQL Cluster Manager 8.3.0 (2024-01-16, Innovation Release)

Functionality Added or Changed

  • MySQL Cluster Manager now uses the third-part library GLib version 2.78.0. The new GLib version is included in the MySQL Cluster Manager distribution archive. (Bug #35906966)

Bugs Fixed

  • For a cluster without any mysqld nodes, after adding a new process, a rolling restart hung, and then mcmd quit unexpectedly. This was due to the wrong initial status assigned to the added node, and this fix corrects it. (Bug #36092321)

  • The mysqld system variable admin_ssl_cipher was taken by mcmd to be of the file name data type, which was wrong. With this fix, mcmd now recognizes it as string. (Bug #36082159)

  • In some rare occasions, an mcmd agent quit unexpectedly when it tried to recover itself. That was due to some incorrect locking happening when multiple threads accessed the data repository together. This fix implements the correct locking. (Bug #36072282)

  • When restoring a backup, the error message only said that the restore failed when the password for the backup was not properly supplied. With this fix, the error message made it clear when the password file did not exist, or when the password was invalid. (Bug #36022311)

  • On Unix-like platforms, the process name for mcmd has been changed to main since release 8.1.0. The name is now changed back to mcmd to make it easier to monitor the process with the ps command. (Bug #35948991)

  • When mcmd was running on Windows platforms, there were too many "Async queue pop timeout" warnings, making it hard to read the log. The threshold for issuing the warning is now raised to 0.5s to avoid unnecessary warnings. (Bug #35463580)

  • When starting mcmd, a user named root could be set up for connection from a client, even if mcmd was not being run by root. That is now disallowed. (Bug #34999007)