Dear MySQL users,
MySQL Cluster Manager 1.2.3 has been released and can be downloaded from
Documentation on using MySQL Cluster Manager can be found at
http://dev.mysql.com/doc/mysql-cluster-manager/1.2/en/index.html and the release notes
are available from
MySQL Cluster Manager offers three core capabilities to boost productivity and simplify
- Automated management
- Monitoring and self-healing recovery
- High availability operation
MySQL Cluster Manager is a part of the commercial MySQL Cluster Carrier Grade Edition
Andrew Morgan - MySQL High Availability Principal Product Manager.
Functionality Added or Changed
Agent; Important Change: The default user name for MySQL Cluster Manager MySQL user
accounts has been changed from admin to mcmd. See "Setting the MySQL Cluster Manager
Agent User Name and Password"
Client: The restore cluster command now supports restoring MySQL Cluster distributed
privileges, using the --privilege-tables option added in this release. In addition, it is
now possible to use IDs of SQL nodes as well as data nodes with the --skip-nodeid option.
Agent; Important Change: The default location for the agent data directory has been
changed to /opt/mcm_data.
Agent; Important Change: MySQL Cluster Manager did not support many of the changes in,
additions to, or removal of mysqld configuration attributes in MySQL Server 5.6 and MySQL
Cluster NDB 7.3. The agent now knows about these changes. For information about these
changes from MySQL 5.5 and MySQL Cluster NDB 7.2, see "What Is New in MySQL 5.6"
MySQL Cluster NDB 7.3.1 is currently available as a Developer Milestone
Release; for more information, see "MySQL Cluster NDB 7.3"
Agent: mcmd could fail to restart when the host system was restarted.
Agent: By default, the tmpdir for mysqld processes was set to datadir/tmp, which caused it
to be treated as a database by the mysql client. Now the tmp directory in the MySQL
installation directory is used by default.
Client: mcm client commands that failed due to the presence of extraneous characters
following short options did so with no information about the cause. Now in such cases, a
specific error message is issued in the client.
Client: The backup cluster command timed out when used with a cluster whose name contained
exactly 8 bytes.
Client: The mcm client set command tried to handle values passed with the
slave_skip_errors configuration attribute as wrong type (as booleans rather than
strings), and failed.
|• MySQL Cluster Manager 1.2.3 has been released||Andrew Morgan||2 May|