MySQL Cluster Manager 8.0 Release Notes  /  Changes in MySQL Cluster Manager 8.0.30 (2022-07-26, General Availability)

Changes in MySQL Cluster Manager 8.0.30 (2022-07-26, General Availability)

Deprecation and Removal Notes

  • Agent: The command-line format of the following options has been deprecated:

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

Functionality Added or Changed

  • Agent: The update process command can now be run on a process that is in the starting status. Typical use case for this is: when mcmd looses control of a mysqld node due to a timeout of the start process on it, once the issue is fixed on the node, update process can be run to re-establish control of the node by mcmd. (Bug #32779154)

  • Client: With the release of MySQL Enterprise Edition 8.0.30, the MySQL Enterprise Encryption functions are now provided by a component. The set command of the mcm client can now be used on the component's system variables (see Configuring MySQL Enterprise Encryption for descriptions of the system variables). (Bug #34104948)

  • Client: When no data nodes are available, a set command that restarts a mysqld node without also restarting the data nodes is now rejected. This is to make sure that issues with the data nodes are first handled, so that the mysqld restart will actually be successful. (Bug #33617571)

  • Client: The following errors have been added to cover a number of issues that the collect logs command might run into:

    • ERROR 5502 Cannot announce TCP port n on host

    • ERROR 5503 No clients connected for n seconds

    • ERROR 5504 No reader progress while collecting files

    • ERROR 5505 Error reading from remote agent host

    • ERROR 5506 File copy failed to host

    • ERROR 5507 Server host refusing connections from client host

    • ERROR 5508 Server host reset connection from client host

    (Bug #26619287)

  • MySQL Cluster Manager now uses the third-part library GLib version 2.72.0. The new GLib version is included in the MySQL Cluster Manager distribution archive. (Bug #34209408)

Bugs Fixed

  • Agent: The success message from the delete cluster and delete backup commands now includes information on the number of warnings issued, when applicable. (Bug #34237041)

  • Agent: Occasionally, the mcmd agent quit unexpectedly if the handshake was aborted somehow during a connection attempt by an mcm client. (Bug #34197655)

  • Agent: When a configuration option for mcmd that cannot be set in a configuration file was set there, or when an option is specified in the wrong section of the configuration file (see mcmd, the MySQL Cluster Manager Agent for explanations), mcmd was still started successfully, while the options were not actually set. With this patch, mcmd throws an error instead in the situation. (Bug #34119635)

  • Agent: Setting --copy-port=0 caused mcmd to throw an error with the message that the value was not in the allowed range, while it actually was. (Bug #34114479)

  • Agent: Occasionally, the mcmd agent quit unexpectedly while parsing event records from an ndb_mgmd node. (Bug #32922993)

  • Client: The delete cluster command always reported success as long as it could finish its reconfiguration plan, even if some files or folders for the cluster could not be deleted. With this fix, the command reports "Cluster deleted successfully, but some files remain" when that is the case. (Bug #28949053)