MySQL Cluster Manager 8.1 Release Notes  /  Changes in MySQL Cluster Manager 8.1.0 (2023-07-18, Innovation Release)

Changes in MySQL Cluster Manager 8.1.0 (2023-07-18, Innovation Release)

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 from OpenSSL 1.1.1 to OpenSSL 3.0. The exact version is now 3.0.9. More information on changes from 1.1.1 to 3.0 can be found at html. (Bug #35386681)

  • Client: The --background option for the mcm client commands have been deprecated. A warning is issued to mcmd.log when the option is used. (Bug #35243651)

  • Encrypted connections are now supported by MySQL Cluster Manager. See Using Encrypted Connections for details. (Bug #35092385)

Bugs Fixed

  • Agent: mcmd could not be run as a service on a Linux platform unless a PID file was configured in the DEFAULT section in the mcmd configuration file, which should not be necessary. (Bug #35396661)

  • Agent: The command-line format of the following options has been deprecated since release 8.0.30, and it can no longer be used now:

    Use the --mcmd.[option] format instead, or specify the options in the configuration file. (Bug #35232312)

  • Agent: The show status command can now be used without any options, in which case the runtime information of the mcmd agent the client connected to is returned. (Bug #35093097)

  • Client: Users did not receive a warning message when packages supported on an experimental basis were added (for example, when the package added was of an NDB version that was ahead of the MCM version being used). A warning is now issued in the situation. (Bug #35457886)

  • Client: Setting the mysqld system variable audit_log_format to the value JSON using the mcm client resulted in an error and the complaint that the value was illegal. (Bug #35367868)

  • Client: Client authentication failed for mcm with "(using password: NO)" in the error message if a password was supplied and the option --default-auth was set to a method other than caching_sha2_password. (Bug #35233284)