List:General Discussion« Previous MessageNext Message »
From:Hery Ramilison Date:August 15 2014 10:22pm
Subject:MySQL Cluster Manager 1.3.2 has been released
View as plain text  
Dear MySQL users,

MySQL Cluster Manager 1.3.2, has been released and can be downloaded
from the My Oracle Support (MOS) website. It will also be available
on Oracle Software Delivery Cloud at http://edelivery.oracle.com with
the September update in a few weeks.

MySQL Cluster Manager is an optional component of MySQL Cluster Carrier
Grade Edition - providing a command-line-interface that automates common
management tasks. These include these on-line operations:
  - Configuring and starting MySQL Cluster
  - Upgrades
  - Addition of new nodes
  - Configuration changes
  - Backup and restore
MySQL Cluster Manager is a commercial extension.
More details can be found at http://www.mysql.com/products/cluster/mcm/

A brief summary of changes in MySQL Cluster Manager version 1.3.2 is 
listed below:

Functionality Added or Changed (2014-08-15)

   * Agent; Client: In order to improve execution robustness, MySQL
     Cluster Manager now fails any commands that reconfigure a
     cluster with a message (i.e. "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
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-cluster.html)
     or import config
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html)
     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)

Bugs Fixed

   * 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)

   * Agent; Client: The import config
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html)
     command did not import configuration settings from a cluster's
     my.cnf file properly; problems included:

        + Some settings in the [mysqld] section were left out (for
          example, key_buffer_size and query_cache_type).

        + Some options in the [client] section were included by
          mistake.

        + The !include and !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 loose_ and maximum_ were not
          recognized.

        + Option group for specific release series (for example,
          [mysqld-5.6]) were not imported.
     (Bug #19078129)

   * Agent; Client: When the configuration of a running cluster was
     being imported using the import config
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html)
     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
     MaxNoOfExecutionThreads parameter in config.ini, which is
     supposed to set the thread configuration when ThreadConfig is
     not specified in 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
     configuration. (Bug #19032714)

   * Agent; Client: The import config
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html)
     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; Client: When using the import config
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html)
     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 configuration.
     (Bug #18651726)

   * Agent: The MySQL Cluster Manager agent might crash when
     running an import config
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html)
     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: 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
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-backup-cluster.html)
     , restore cluster
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-restore-cluster.html)
     , abort backup
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-abort-backup.html)
     , or import cluster
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-cluster.html).
     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.
     (Bug #18781345)

   * Client: Restoration of a cluster failed when the cluster
     contained both API nodes with and without specified hostnames.
     (Bug #19313429)

   * Client: If a mysqld process was specified in a create cluster
     statement using the mysqld@* syntax (with no host specified),
     the show status --process commands would never show the
     process as connected, even when it was. (Bug #19152161)

   * Client: When using the show status

(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-show-status.html)
     command with the --backup option, 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
     --backup. (Bug #19032714)

   * Client: MySQL Cluster Manager threw an error when the add
     package
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-add-package.html)
     command was run with the argument for the --basedir 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. (Bug #18973711)

   * 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 using the import config
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html)
     command, some process level settings in the cluster's config.ini
     file were imported as instance level settings. (Bug #18651663)

   * Client: When the configuration of a running cluster was being
     imported, the import config
(http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html)
     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)

You can also find more information on the contents of this release in
the change log:
http://dev.mysql.com/doc/relnotes/mysql-cluster-manager/1.3/en/mcm-news-1-3-2.html

The user manual can be found at:
http://dev.mysql.com/doc/index-cluster.html

Your feedback is greatly appreciated!

Please report any problems you have at https://bug.oraclecorp.com/

Enjoy!

On Behalf of the MySQL/ORACLE RE Team,
Hery Ramilison
Thread
MySQL Cluster Manager 1.3.2 has been releasedHery Ramilison15 Aug 2014