Skip navigation links
MySQL Cluster Manager 1.1 Release Notes :: Changes in MySQL Cluster Manager 1.1.1 (2011-07-11)
»
Section Navigation      [Toggle]

Changes in MySQL Cluster Manager 1.1.1 (2011-07-11)

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

Functionality Added or Changed

  • Agent; Incompatible Change: The identifiers mysql-cluster-manager and mysql-proxy have been replaced with mcmd. This has the following effects:

    1. The script bin/mysql-cluster-manager used to start the MySQL Cluster Manager agent is now bin/mcmd.

    2. The name of the default agent configuration file etc/mysql-cluster-manager.ini has been changed to etc/mcmd.ini.

    3. The default agent log file mysql-cluster-manager.log is now named mcmd.log.

    4. The default PID file mysql-cluster-manager.pid, if used, is now named mcmd.pid.

    5. Within the agent configuration file, the [mysql-proxy] section heading has been replaced with the heading [mcmd].

    These changes are not compatible with previous versions of MySQL Cluster Manager. In particular, the old configuration file section heading [mysql-cluster-manager] is not recongized by MySQL Cluster Manager 1.1.1 and later; you must use [mcmd] instead.

  • Agent; Important Change: When starting the MySQL Cluster Manager agent, the --defaults-file option is no longer required. The agent now tries by default to find and use the configuration file etc/mcmd.ini (in the MySQL Cluster Manager installation directory). The default can still be overridden using this option. See Starting and Stopping the MySQL Cluster Manager Agent, for more information.

  • Client; Important Change: Formerly, the show status client command required the use of one of the options --cluster (short form: -c), --operation (-o), or --process (-r). Now, if none of these options is specified, --cluster is assumed. For more information, see The show status Command.

  • Client; Important Change: Added the stop agents client command, which can be used to stop one, some, or all of the MySQL Cluster Manager agents in a given management site.

    For more information, see The stop agents Command.

  • Important Change: MySQL Cluster Manager now supports multiple clusters. Each process-host used by a cluster, as specified in the --processhosts (-R) option of the create cluster command used to create that cluster, must not be used in any other cluster.

    See The create cluster Command.

Bugs Fixed

  • Agent: The MySQL Cluster Manager Agent failed to start when the agent configuration file had the wrong Unix permissions. (Bug #11766449)

    References: See also Bug #11907655.

  • Agent: The MySQL Cluster Manager agent failed to start when the same path was used for log-file and manager-directory. (Bug #11756597)

  • Agent: Trying to start a cluster whose management server used a port already in use by a management server in a different cluster timed out instead of failing with an error. (Bug #11759740, Bug #52073)

    References: See also Bug #11760416, Bug #52827.

  • Agent: Trying to start a cluster with an SQL node using a socket file already in use by an SQL node in a different cluster timed out instead of failing with an error. (Bug #11760416, Bug #52827)

    References: See also Bug #11759740, Bug #52073.

  • Client: When a site was created specifying a hostname, and IP to hostname lookup later failed, the Hosts column in the output of the list hosts command showed Unknown for that host. (Bug #11765645)

Copyright © 2009, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices