This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.3.0 since the final release of MySQL Cluster Manager 1.2.
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
logs command added in this release.
MySQL Cluster Manager can now take a standalone MySQL Cluster under its own
control using the
cluster command implemented in this release, and
manage this cluster just as if it had been created in the
In addition, the
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
import; in addition, none of the commands
process can be used with this cluster until the
cluster has been prepared using
For more information about these commands, see
import cluster Command, and
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.
MySQL Cluster Manager normally assigns IDs to new node processes automatically
(although this can be overridden when issuing
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
log command for the mcm client has
been added in this release, to enable and configure log rotation
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
x.y.z is the version number of the
current release. The former top-level directories such as
etc are now found within this
For more information, see Installing MySQL Cluster Manager on Unix Platforms.
Important Change; Client:
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
--removedirs option added in this release.
Agent: Using hosts with different package locations in the same cluster did not work. (Bug #17491230)
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
of any option files, and ignores all other sections.
Now when you attempt to start a mysqld
process in a cluster that is stopped, or in which the data nodes
are otherwise unavailable,
fails with an error.
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)