This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.1.2 since the release of MySQL Cluster Manager version 1.1.1.
Quick Test Setup of MySQL Cluster
Agent; Important Change: Added the
--bootstrapoption for mcmd. Starting the agent with this option causes it to create and start a single-machine MySQL Cluster on the current host. This cluster—named
mycluster—has a default configuration suitable for simple testing.
myclusterconsists of 1 management node, 2 data nodes (both using ndbd), and 2 SQL nodes, with an open connection slot available for an additional API node. The data nodes are configured by default to use 75 MB for data memory and 15 MB for index memory.
For more information, see Starting and Stopping the MySQL Cluster Manager Agent.
Bundled MySQL Cluster
Important Change; Packaging: It is no longer necessary to download and install MySQL Cluster Manager and MySQL Cluster separately; all MySQL Cluster Manager 1.1.6 packages include the MySQL Cluster NDB 7.1.15a binary distribution. Following installation, the MySQL Cluster distribution may be found in the
clusterdirectory, under the MySQL Cluster Manager installation directory.
mcm Command-Line Client
Important Change: The MySQL Cluster Manager distribution now includes its own command-line client mcm, which can be found in the installation
bindirectory. mcm can be used in place of the mysql client, and reduces the number of options required to connect to the MySQL Cluster Manager agent.
An mcm (or mcm.exe) binary on a given host can connect to mcmd (or mcmd.exe) running on a host that uses a different operating system or hardware; the communication protocol used by MySQL Cluster Manager is platform-agnostic.
It is still possible for a standard mysql client to connect to a MySQL Cluster Manager agent; this can be used to administer clusters from hosts where the mcm client is unavailable.
For more information, see Starting the MySQL Cluster Manager Client.
Agent: If DNS lookup fails while mcmd is attempting to connect to a cluster mysqld process by host name, mcmd retries the connection using IP address 127.0.0.1. However, the retry failed because the MySQL client library treated it as an attempt to connect using a socket, rather than by TCP. Now in such cases, the client library's behavior is overridden so that the retry is always made using TCP and IP address 127.0.0.1. (Bug #12915751)
Although MySQL Cluster data nodes must use node IDs in the range 1-48 inclusive (see Limits and Differences of MySQL Cluster from Standard MySQL Limits), it was possible for data nodes to be assigned IDs outside this range. Now MySQL Cluster Manager reserves this range of node IDs for data nodes. (Bug #11766629, Bug #59778)