Client: In the event of major problems with a MySQL Cluster, it is often necessary to collect all of the cluster's log and configuration files and to send or to copy these off-site for analysis. Formerly, this had to be done manually, or by using the ndb_error_reporter utility included with the MySQL Cluster distribution, but it is now possible to accomplish this task from within the mcm client, using the collect logs command added in this release. (Bug #11757603)

Agent; Client: MySQL Cluster Manager can now take a standalone MySQL Cluster under its own control using the import cluster command implemented in this release, and manage this cluster just as if it had been created in the mcm client.

In addition, the create cluster command has been enhanced with an --import option, which identifies the cluster as having been created as a target for importing a cluster; such a target cluster can be identified in the output of show status --process as import; in addition, none of the commands start cluster, restart cluster, start process, or stop process can be used with this cluster until the cluster has been prepared using import cluster.

For more information about these commands, see The import cluster Command, and The create cluster Command. For information about the process required for importing a new MySQL Cluster into MySQL Cluster Manager, see Importing MySQL Clusters into MySQL Cluster Manager. (Bug #17480585)

Client: MySQL Cluster Manager normally assigns IDs to new node processes automatically (although this can be overridden when issuing create cluster or add process). The list nextnodeids command added in this release prints the next node ID that has been reserved for the next new process of each type added to the cluster named cluster_name.

Agent; Client: A new rotate log command for the mcm client has been added in this release, to enable and configure log rotation for mcmd. (Bug #16982252)

Important Change; Packaging: The directory structure of the MySQL Cluster Manager distribution archive has changed. The top level within the archive now contains a single directory named mcm-x.y.z, where x.y.z is the version number of the current release. The former top-level directories such as bin, libexec, and etc are now found within this mcm-x.y.z directory.

For more information, see Installing MySQL Cluster Manager on Unix Platforms.

Important Change; Client: The delete cluster command no longer removes configuration or data directories for cluster processes by default. Now, such directories are removed only when this command is invoked with the --removedirs option added in this release. (Bug #17455398)

Agent: Using hosts with different package locations in the same cluster did not work. (Bug #17491230)

Client: Setting the user or password option (or both) in a my.cnf file caused the MySQL Cluster Manager client to fail on startup with the error Illegal username or password. As part of the fix for this issue, the MySQL Cluster Manager client now reads only the [mcm] section of any option files, and ignores all other sections. (Bug #17540585)

Client: It was possible to start an SQL node, using the start process command, in an otherwise stopped cluster. In addition, this node could not be stopped using stop process afterwards.

Now when you attempt to start a mysqld process in a cluster that is stopped, or in which the data nodes are otherwise unavailable, start process fails with an error. (Bug #17073352)

Client: The mcm client tried to add mysql client options which must be specified first on the command line in the wrong order. Now the mcm client checks for such options and makes sure that they are passed to mysql first. (Bug #16598776)