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

Changes in MySQL Cluster Manager 8.0.29 (2022-04-26, General Availability)

Functionality Added or Changed

  • Agent: Previously, mcmd ignored any unknown configuration options. A new configuration option, unknown_config_option, has now been introduced, and it accepts the following values:

    • error (the default setting): mcmd returns an error when an unknown option is encountered

    • warning: mcmd prints a warning when an unknown option is encountered and continues with starting.

    (Bug #33581159)

  • The start process command can now be used to start a specific type or list of nodes. See the description of the command for details. (Bug #33934457)

  • When a backup ID has been specified with the --backupid option for a backup cluster, restore cluster, abort backup, or delete backup command, any leading zeros of the ID are dropped. This patch adds a warning when this happens, so the user knows if an unintended ID has been used. (Bug #33805006)

Bugs Fixed

  • Agent: The remove process command allowed duplicated process ID entries. With this fix, an error is thrown when a process ID is repeated in the command. (Bug #33844469)

  • Agent: When bootstrapping an NDB 8.0 cluster, mcmd did not set the mysqlx_port and mysqlx_socket system variables for mysqld, resulting in errors appearing in the mysqld log. With this fix, those system variables are now properly set at bootstrapping. (Bug #33729859)

  • Agent: Multiple sinks for mcmd logging could not be configured individually by the mcmd configuration file, so that all the sinks worked in the same manner. (Bug #33650263)

  • Client: mysqld options for the validate_password plug-in were not recognized, and setting any of them using the mcm client resulted in an error. (Bug #33901017)