MySQL Cluster Manager 8.0 Release Notes  /  Changes in MySQL Cluster Manager 8.0.33 (2023-04-18, General Availability)

Changes in MySQL Cluster Manager 8.0.33 (2023-04-18, General Availability)

Functionality Added or Changed

  • The README file has been updated with corrections and improvements. (Bug #35208333)

  • Starting from release 8.0.33, there is no upgrade path from MySQL Cluster Manager 1.4 to 8.0 except via 1.4.8. For release 1.4.7 or earlier, upgrade to 1.4.8 first, and then to 8.0.

Bugs Fixed

  • Agent: When reporting the total number of active mcm client connections, mcmd always reported instead the total number of connections made since it started. (Bug #35096409)

  • Agent: mcmd sent a 8-bit scramble to a client that was trying to connect, while a 7-bit one was required, causing authentication to fail sometimes. (Bug #35014240)

  • Agent: The mcmd help output has been improved with corrections and reorganization. (Bug #34899135)

  • Agent: When the same port number was used to configure more than one connection port, mcmd started as usual and failed eventually. With this fix, mcmd throws an error immediately in the situation and refuses to start. (Bug #34891286)

  • Agent: When mcmd was started and it printed the message on how to connect to it, it always printed the name of the host on which mcmd was running, but ignored the bind_address that had been set. Also, the port number in the message was wrong, unless it had been set with the deprecated bind-port option. (Bug #34694458)

  • Agent: Success message of the upgrade cluster command has been changed to cover both upgrades and downgrades. (Bug #34503870)

  • Client: The mcm client lost connection to mcmd as it executed another command after show status. (Bug #34943145)

  • Client: mcm misidentified itself as a mysql client in the system log. (Bug #34894735)