2 Changes in MySQL Cluster Manager 9.5.0 (2025-10-23, Innovation Release)

Note

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

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

Functionality Added or Changed

Agent: The libxml2 library bundled library bundled in the Windows distribution of MySQL Cluster Manager has been upgraded to version 2.14.5. (Bug #38198545)
Client: MySQL Cluster Manager now uses the third-party library GLib version 2.84.3. The new GLib version is included in the MySQL Cluster Manager distribution archive. (Bug #38198580)

OperationBegin and OperationEnd events are now logged to the event log for the agent connected to the client. The output looks similar to the following:

1754993119061902;1;create site --hosts=100.103.24.29,100.103.24.180 mysite
1754993119384512;100;10129;{30e31bae 1 0}
1754993119393989;101;10129;{30e31bae 1 0};0
1754993119394073;2;333;0

(Bug #38229518)

The advisor mechanism was extended with the following:
- A new CLI command, list advice.
- Cluster DataMemory advice
- mcmd disk usage advice.
- mcmd RAM usage advice. An event was also added to the eventlog for both the high and normalized cases.
- mcmd CPU usage advice. An event was also added to the eventlog for both the high and normalized cases.
- mcmd agent missing or disabled TLS configuration advice.
- mcmd agent default credentials advice. This is only visible through the list advice command.
- Threshold checking for the advice, so it does not fire again until the average drops below the threshold.
(Bug #38037622, Bug #38394698, Bug #38386063, Bug #38364624, Bug #38359140, Bug #38352225, Bug #38331179, Bug #38037652, Bug #38423571, Bug #38423550)

Bugs Fixed

Agent: The mcmd event log was not reloaded on mcmd startup. As of this release, if an event log exists, it is reloaded. (Bug #38222837)
Under certain circumstances, the event log could write incorrect timestamps to file. (Bug #38224675)
The backup advisor only triggered once if no backup was performed. As of this release, it triggers each time the defined period is reached. (Bug #38210378)