MySQL Cluster Manager 1.3.3 has been released (no replies)

Dear MySQL users,

MySQL Cluster Manager 1.3.3, has been released and can be downloaded
from the My Oracle Support (MOS) website. It will also be available
on Oracle Software Delivery Cloud at http://edelivery.oracle.com with
the next monthly update.

MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier
Grade Edition, providing a command-line interface that automates common
management tasks, including the following online operations:
 - Configuring and starting MySQL Cluster
 - Upgrades
 - Addition of new nodes
 - Configuration changes
 - Backup and restore

MySQL Cluster Manager is a commercial extension to the MySQL family of products.
More details can be found at http://www.mysql.com/products/cluster/mcm/

A brief summary of changes in MySQL Cluster Manager version 1.3.3 is listed below:

Changes in MySQL Cluster Manager 1.3.3 (2014-12-01)

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

   Functionality Added or Changed

     * Agent: For a node on which an expected backup is not found,
       the output for the list backups command now reads "None"
       for BackupId and says "No backups". (Bug #19208671)

     * A remove process command has been added, providing a means
       to perform an offline scale down for a cluster.
       See Section 4.6.6, The remove process Command, for details.

   Bugs Fixed

     * Agent: When a cluster was in single-user mode, any mcm command
       that causes a configuration change and a subsequent rolling
       restart (for example a set, add process, or a restart cluster)
       would stop the first data node in each nodegroup and would then
       be unable to restart it, due to a limitation with the MySQL
       Cluster. With this fix, mcm rejects those commands under the
       situation with an error message, instead of letting the data
       nodes be stopped. (Bug #20026523)

     * Agent: When MySQL Cluster Manager was trying to create a
       temporary directory (tmpdir) for a MySQL node under its
       directory for manager data (manager-dir), it did not
       always follow the specification for manager-dir for the
       node, which resulted in putting the temporary directory
       at the wrong location sometimes. (Bug #20026523)

     * Agent: When the --log-use-syslog option was set during
       the startup of mcmd, an error was thrown, complaining
       that the option log-file was also used (which is not
       allowed) even if --log-file was not really set. (Bug
       #19972864)

     * Agent: If a data node went from the running into the
       added state for some reasons, it became irrecoverable by
       MySQL Cluster Manager because, as a safeguard, MySQL
       Cluster Manager did not start a newly added data node
       automatically when the cluster was running. The safeguard
       is now removed, in order to allow the recovery of a data
       node in the described situation. (Bug #19787156)

     * Agent: During the recovery of an mcmd agent from a crash,
       if the cluster's management node could not be contacted
       for information, the agent just reported the statuses of
       the managed processes as they were last known, which
       might not reflect the processes' real statuses (for
       example, a process might have just crashed, and the agent
       would still said it is running), With this fix, the mcmd
       agent will report the statuses of the processes as
       "unknown" in the described situation. (Bug #19321446)

     * Agent: When bootstrapping a default cluster with the
       --bootstrap option, the ndbd process was used for data
       nodes. With this fix, the multi-threaded ndbmtd process
       is used instead, which is preferable from a performance
       perspective. (Bug #18068338)

     * Agent: An mcmd agent crashed when trying to stop a
       cluster that was hanging during an operation to restore
       itself. (Bug #17957393)

     * Agent: Configuration attribute values that start and end
       with double quotes could not be set using the set
       command. (Bug #13040122)

     * Client: When setting the LogDestination configuration
       attribute using the set command, mcm threw a syntax error
       when the attribute's value was single-quoted. (Bug
       #19435351)

     * Client: The error reporting for a data node crash by the
       MySQL Cluster Manager client did not include what had
       been reported by the ALERT statements before. With this
       fix, "ALERT" is included as a matching pattern for
       picking up errors from logs of the data nodes, which
       might result in more information on the crash being
       provided. (Bug #19426279)

     * Client: At an attempt to add to a site a host that
       already belonged to another site, the MySQL Cluster
       Manager client hung; and even after the client was
       restarted, proper control of the agent (to which the
       client was connected) could be recovered only after the
       site (to which the add hosts attempt was made) was
       deleted. With this fix, MySQL Cluster Manager checks if
       the host already belong to some other sites when the
       create site or add hosts commands are issued, and throws
       an error if that is the case. (Bug #18424613)

     * Client: A newline contained inside a multi-line set
       command caused mcm to throw an error. (Bug #11759662, Bug
       #51992)


You can also find more information on the contents of this release in
the change log:
http://dev.mysql.com/doc/relnotes/mysql-cluster-manager/1.3/en/mcm-news-1-3-3.html

The user manual can be found at:
http://dev.mysql.com/doc/index-cluster.html

Your feedback is greatly appreciated!

Please report any problems you have at https://bug.oraclecorp.com/

Enjoy!

On Behalf of the MySQL/ORACLE RE Team,
Kent