Changes in MySQL Cluster Manager 9.4.0 (2025-07-23, Innovation Release)

Note

These release notes were created with the assistance of MySQL HeatWave GenAI.

Version 9.4.0 is the latest innovation Release of the MySQL Cluster Manager. It is intended for use with MySQL NDB Cluster 9.4 and 8.4, but also supports the 8.0 series.

• Functionality Added or Changed

• Bugs Fixed

Functionality Added or Changed

• Agent: The libxml2 library bundled in the Windows distribution of MySQL Cluster Manager has been upgraded to version 2.14.4. (Bug #38073806)

• Agent: A new advisor mechanism has been created for MySQL Cluster Manager. Currently, only one advisor is provided: a backup advisor gives a warning when a cluster backup has not been performed in the last 24 hours. The warning can be queried with the list warnings command. (Bug #37886705)

• Agent: XCom communications among mcmd agents can now be encrypted with TLS to enhance security for the system. (Bug #35549980)

• Agent: There is now an event log (mcmd_eventlog.csv) that records major events for MySQL Cluster Manager (system information, beginnings and completions of commands and processes, etc.). The event log is found in the folder specified by the --logging_folder option, and is collected by the collect logs command. (Bug #35042269)

Bugs Fixed

• Agent: The sample_mcmd.conf file has been updated to have the mcmd_password entry uncommented. That makes the file consistent with the requirement since release 9.3.0 that a user-defined mcmd password must be added to the configuration file. (Bug #38031559)

  References: See also: Bug #37457513.

• Agent: The upgrade cluster command did not reject invalid downgrade paths for MySQL NDB Clusters (for example, from one innovation release to another). (Bug #37921613)

• Agent: The stop process command timed out on a non-running node that had been successful added by a command that failed subsequently. With this fix, the stop process command returns success in this scenario. (Bug #37889501)

• Client: When a path to a file instead of a folder is given with the add package command as the argument for the --basedir option, the mcm client complained that the file did not exist. With this fix, mcm throws the proper error and complains on the wrong path type. (Bug #37808054)