This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.3.2 since the release of MySQL Cluster Manager version 1.3.0.
Functionality Added or Changed
Agent; Client: In order to improve execution robustness, MySQL Cluster Manager now fails any commands that reconfigure a cluster with the message ERROR 5027 Unable to perform command due to utility <proc_name> with pid <ospid> on <host> if any utility process (for example, mysql_upgrade, mysql_install_db, or ndb_restore) that was started by a previous command is still remaining (running or hung) on any host when the command is issued. (Bug #18966650)
Client: MySQL Cluster Manager now throws an error if the user tries to import a cluster or a cluster configuration using the import cluster or import config command while the user who runs the mcmd process does not have permissions to the cluster processes' PID files. This happens typically when mcmd is started with the user “mysql” while the cluster is started with “root.” (Bug #18887139)
Agent; Client: On Windows platforms, when a data node could not be restarted during a rolling restart of the cluster, it was not reported to the user. With this fix, the user now gets a report when a maintenance restart of a data node failed. (Bug #19227535)
The import config
command did not import configuration settings from a cluster's
my.cnf file properly; problems included:
Some settings in the
were left out (for example,
Some options in the
were included by mistake.
!includedir statements for including
settings from other files were ignored
Quoted values were not handled properly—the quotes were taken literally.
Lines starting with “;” were not treated as comments.
The option modifiers
maximum_ were not recognized.
Option group for specific release series (for example, [mysqld-5.6]) were not imported.
When the configuration of a running cluster was being imported
using the import
config command, even if the parameter
ThreadConfig was not
defined in the
config.ini file, its value
could be imported from the running node's setting for it. The
imported value overrode the configuration prescribed by the
config.ini, which is supposed
to set the thread configuration when
ThreadConfig is not
config.ini. This fix prevents
the import of the value for
ThreadConfig from the
running node, making MySQL Cluster Manager rely on the
config.ini file for the thread
When using the import
config command, the format of an imported configuration
setting was sometimes changed from that which was used in the
config.ini file—for example, a value
in megabytes was imported as a value in bytes and then shown as
such by the get command. That made it more
difficult for the user to compare the original and the imported
value. This fix makes MySQL Cluster Manager follow the original format in the
config.ini file when importing a cluster's
Agent; Client: The import config command sometimes imported MySQL server default values that were not specified in the cluster's configuration files. With this fix, no such values are imported. (Bug #18651301)
Agent: The MySQL Cluster Manager agent might crash when running an import config command if it was managing more than one cluster at the time. (Bug #19380825)
Agent: During a recovery for a MySQL Cluster Manager agent that uses IP addresses instead of hostnames, the agent sent out an excessive amount of information, the processing of which slowed down the restart process considerably. This fix changes the way the IP addresses are handled, reducing the amount of sent information to a much more reasonable level. (Bug #19269735)
Agent: When a wild cluster's process PIDs were not available to MySQL Cluster Manager, executing an import cluster command resulted in a process error and the complaint that a process handle could not be opened. With this fix (which is a side effect of the fix for Bug #19209870), MySQL Cluster Manager no longer attempts to open the handles for unknown PIDs. (Bug #19205183)
Agent: Upgrade from MySQL Cluster Manager 1.2.4 (to 1.3.1) failed if the last command executed before the upgrade was any one of backup cluster, restore cluster, abort backup, or import cluster. This has been fixed, and users of version 1.2.4 can now upgrade to version 1.3.2. (Bug #19199645)
Agent: The MySQL Cluster Manager agent sometimes got SIGABRT errors while executing SQL statements. (Bug #19032927)
Agent: mcmd crashed due to an out-of-memory error after a combination of the following conditions:
An abrupt failure of one of the site machines, instead of a clean stop.
Only a minority of the agents are available.
Some unmanaged SQL slots came into use and changed their states to “connected,” and the changes are reported by a ndb_mgmd process.
Client: Restoration of a cluster failed when the cluster contained both API nodes with and without specified hostnames. (Bug #19313429)
mysqld process was specified in a
create cluster statement using the
mysqld@* syntax (with no host specified), the
commands would never show the process as connected, even when it
When using the show
status command with the
the MySQL Cluster Manager client sometimes accepted an additional option, which
was actually meaningless. This fix makes the client throw an
error when any other option is used in combination with
MySQL Cluster Manager threw an error when the
add package command was
run with the argument for the
option being double quoted, complaining the path did not exist.
It was because MySQL Cluster Manager took the double quotes literally, as parts
of the path name.
Client: On Windows platforms, the MySQL Cluster Manager client's response to the list hosts command was very slow when any one of the MySQL Cluster Manager agents was down. (Bug #18966650)
Client: When the configuration of a running cluster was being imported, the import config command took the settings from the global session variables instead of the configuration files of the cluster and the MySQL servers. This fix makes MySQL Cluster Manager import the settings from the configuration files, and only use values of the global session variables when it cannot find, open, or access the configuration files. (Bug #18652366)
When using the import
config command, some process level settings in the
config.ini file were imported as
instance level settings.