This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.2.3 since the release of MySQL Cluster Manager version 1.2.2.
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
x.y.zis the version number of the current release. The former top-level directories such as
etcare now found within this
For more information, see Installing MySQL Cluster Manager on Unix Platforms.
Important Change; Agent: The default location for the agent data directory has been changed to
/opt/mcm_data. (Bug #16521396)
Important Change; Agent: 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.Note
MySQL Cluster NDB 7.3.1 is currently available as a Developer Milestone Release; for more information, see MySQL Cluster NDB 7.3 and MySQL Cluster NDB 7.4.
Agent: mcmd could fail to restart when the host system was restarted. (Bug #16292852)
Agent: By default, the
tmpdirfor mysqld processes was set to
/tmp, which caused it to be treated as a database by the mysql client. Now the
tmpdirectory in the MySQL installation directory is used by default. (Bug #16010476)
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. (Bug #16084783)
backup clustercommand timed out when used with a cluster whose name contained exactly 8 bytes.