Version 9.3.0 is the latest innovation Release of the MySQL Cluster Manager. It is intended for use with MySQL NDB Cluster 9.3 and 8.4, but also supports the 8.0 series.
Important Change: For platforms on which OpenSSL libraries are bundled, the linked OpenSSL library for MySQL Cluster Manager has been updated to version 3.0.16. Issues fixed in OpenSSL version 3.0.16 are described at https://openssl-library.org/news/openssl-3.0-notes/. (Bug #37656086)
Important Change: The
libxml2library bundled in the Windows distribution of MySQL Cluster Manager has been upgraded to version 2.13.6. (Bug #37475571)Important Change: Starting from this release, a user-defined
mcmd_passwordmust be provided in the MySQL Cluster Manager Configuration File when starting the mcmd agent, even for bootstrapping, or mcmd will fail to start. As a result, the--passwordoption of the mcm client must also be specified for a client to connect to an agent. (Bug #37457513)Agent: For a bootstrapped cluster, the parameter
StopOnErrorfor ndbmtd nodes is now set tofalseby default, to allow a ndbmtd node to restart automatically after it fails. (Bug #37633409)The
--privilege-tablesoption has been removed from therestore clustercommand. (Bug #37511555)A new client command,
list certs, lists the files created by thecreate certscommand for a cluster. (Bug #36698435)The dependency of MySQL Cluster Manager on the GLib library has been removed, and the library is no longer shipped with MySQL Cluster Manager distributions. (Bug #34613622)
Agent: At the initial startup of a cluster, mcmd emitted the warning that the
high_water_markfile could not be opened. The warning is now removed, as the file is not supposed to exist in the situation. (Bug #37696293)Agent: The
stop processtimed out for processes in theADDEDstate. (Bug #37691818)Agent: The
create certscommand failed after an mcmd agent queried another agent for the certificate authority and key, which were not created by that agent. With this fix, the agent moves on to query another agent in that situation. (Bug #37639369)Agent: The
backup clustercommand failed with an "Access denied" error when themcmd_passwordhad a '#' at the end. (Bug #37609816)Client: A
delete clustercommand failed if the backup's schema file containing the metadata of the NDB tables was missing (for example, due to accidental manual deletion). With this fix, the command works in such situations. (Bug #37660069)Client: At the
debuglog level, the mcmd log prints the wrong comments for some of the planned steps for thecreate certs --renew --certscommand. (Bug #37464246)