MySQL Cluster Manager 1.3 Release Notes  /  Changes in MySQL Cluster Manager 1.3.5 (2015-04-15)

Changes in MySQL Cluster Manager 1.3.5 (2015-04-15)

This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.3.5 since the release of MySQL Cluster Manager version 1.3.4.

Functionality Added or Changed

  • Agent: A site can now be scaled down using the new remove hosts command. (Bug #20677633)

  • Agent: The start up of a new cluster on Windows platforms is now faster due to the reduction of the wait time by mcmd for the bootstrapping of SQL nodes. (Bug #20593752)

  • Client: The upgrade cluster command now supports a --set option, allowing users to set new values for configuration attributes for the upgraded cluster. (Bug #20700483)

  • Client: Execution of client commands is now faster, as unnecessary wait time for events to complete is now eliminated. (Bug #20559800)

  • Client: Error messages for syntax errors involving integers (or lists of integers) in value lists for operands or options have been improved to pinpoint the issues. (Bug #19845253)

Bugs Fixed

  • Agent: When trying to use the delete package command to remove a package from a host with only unmanaged processes, the command failed with an error, complaining that the package is in use by the cluster. (Bug #20719467)

  • Agent: During a cluster restart or recovery, the agent tried to connect too soon to the cluster processes, causing repeated connection failures. This fix makes sure connection attempts to the processes are triggered only when the processes are ready. (Bug #20204375, Bug #19047715)

  • Agent: The list backups command sometimes caused an agent to hang, as another agent on another host might fail to reply to its query for backup information and keep it waiting. (Bug #15854331)

  • Client: In the output of the list backups command, the timestamps for the backups were inaccurate. (Bug #20731491)

  • Client: When applied to the last host on a site, the delete package command failed to remove the package from the host, causing a subsequent delete site command to fail with the error Package exists in site site_name. (Bug #20719467)

  • Client: The suffixes K, M, and G cannot be used when setting the numeric value of a configuration attribute of type DOUBLE, but such use of these suffixes were not rejected by the client. (Bug #20686014)

  • Client: When executing the backup cluster command, the mcm client sometimes hung due to a timeout, because it took too long for the client to receive the message from a node that backup had started. To avoid that, this fix extends the timeout period from 2.5 minutes to 5 minutes. (Bug #20677633)

  • Client: The show warnings command sometimes failed to show warnings triggered by a SET GLOBAL statement, which is sent by mcmd to a mysqld node for setting a dynamic variable. (Bug #20593156)

  • Client: An assertion error occurred when, at an early stage of a recovery, a node failed to fulfill the request for a process status update from another node, because no composite status of the cluster had yet been received. With this fix, the request is ignored, with a warning added to the log. (Bug #20552220)

  • Client: When a backup cluster command's failure was due to a node failure, that was not clearly stated in the error message shown by mcmcd. (Bug #20032694)