This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.1.5 since the release of MySQL Cluster Manager version 1.1.4.
After stopping and restarting the MySQL Cluster Manager Agent with a stopped
cluster, all cluster nodes were shown as having
added for their status rather than
stopped. When the cluster was started
subsequent to this, This caused MySQL Cluster Manager to perform an initial
start of the data nodes, resulting in the loss of the
(Bug #13854142, Bug #13823551)
Changes in some node configuration attributes require data nodes
to be restarted with the
option, but do not require a system restart. Setting any of
these attributes while the cluster was stopped caused all data
nodes to be started with the
resulting in the loss of MySQL Cluster data.
Now in such cases, the set command used to make the change is rejected with an error. The operator can then wait until the cluster is running before trying to change one of these attributes; this update can then be made safely using a rolling restart of the cluster.