This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.2.1 since the release of MySQL Cluster Manager version 1.2.0.
A cluster having an
api process with a
nonexistent host name could not be started. Following an attempt
to do so, the host name could not be changed, nor the process
removed. This situation is now prevented from occurring; if
add process cannot resolve a host name, the
command fails with an appropriate error message.
Agent: In some cases, MySQL Cluster management nodes appeared to hang on shutdown, and MySQL Cluster Manager's connection to it was left open. (Bug #13990350)
References: See also Bug #14730537.