Changes in MySQL Cluster Manager 9.1.0 (2024-10-16, Innovation Release)

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

• Functionality Added or Changed

• Bugs Fixed

Functionality Added or Changed

• Important Change: For platforms on which OpenSSL libraries are bundled, the linked OpenSSL library for MySQL Cluster Manager has been updated to 3.0.15. Issues fixed in OpenSSL version 3.0.15 are described at https://openssl-library.org/news/openssl-3.0-notes/. (Bug #37021997)

• Client: The mcm client has been updated to align with the latest mysql client in terms of its functionality. See Changes in MySQL 9.1.0 for details. (Bug #37023118)

• Client: When a mysqld node quit unexpectedly, the error message given was uninformative. The mcm client now displays error information extracted from the mysqld log in the situation. (Bug #36840761)

• Client: MySQL Cluster Manager now uses the third-party library GLib version 2.80.3. The new GLib version is included in the MySQL Cluster Manager distribution archive. (Bug #36782677)

• Client: The mcm command create certs now gets a new option, --renew, for renewing the TLS keys . See the description of the option for details. (Bug #36556506)

Bugs Fixed

• Agent: The INFO_SRC file in the delivery packages of MySQL Cluster Manager was missing the line on release maturity. (Bug #36924101)

• Client: The error text for the COMMAND_OPTION_DEPENDENCY error was incorrect, with the command name being replaced by the cluster name. (Bug #36954160)

• Client: mcm allowed setting the mysqld system variables telemetry.otel_exporter_otlp_traces_max_tls and telemetry.otel_exporter_otlp_traces_min_tls to an empty string, which was not allowed by the mysqld node and caused the node to fail. With this fix, setting the variables to empty strings are no longer allowed by mcm. (Bug #36508351)