MySQL Cluster Manager 1.3.6 has been released
Posted by: Sreedhar S
Date: July 02, 2015 01:08AM
Date: July 02, 2015 01:08AM
Dear MySQL users, MySQL Cluster Manager 1.3.6, 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 next monthly update. MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier Grade Edition, providing a command-line interface that automates common management tasks, including the following online operations: - Configuring and starting MySQL Cluster - Upgrades - Adding and removing cluster nodes - Adding and removing site hosts - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension to the MySQL family of products. 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.6 is listed below: Changes in MySQL Cluster Manager 1.3.6 (2015-07-02) This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.3.6 since the release of MySQL Cluster Manager version 1.3.5. Functionality Added or Changed * Agent: When a cluster was stopped, it was possible to set an invalid value for the configuration parameter LogDestination, which caused a segmentation fault when the cluster was restarted. With this fix, validation on the value for LogDestination is now performed when it is being set. (Bug #20948621) * Agent: When a "wild" cluster's configuration was being imported with the import config command and the PID files for the cluster processes were available to mcmd, attributes that can only be set at the process type level (for example, MaxNoOfAttributes), if specified differently for different process instances in the cluster's configuration file, received different values for the different process instances. With this fix, when an attempt is made to set such an attribute at the process instance level, mcmd will set the attribute at the process type level instead, and a warning will be issued to the agent log. If the same attempt was made more than once with different values during a configuration import, the last value seen by mcmd will be set, and a warning will again be issued to the log. (Bug #20948149) * Agent: When MySQL Cluster Manager imports a MySQL Cluster of an older version than the one it is itself running on, any deprecated configuration settings are no longer imported; instead, warnings are issued to the agent log that the settings have been skipped during the import. (Bug #20887560) * Agent: A new command, backup agents, has been introduced for backing up mcmd agents' configuration data. For more details, see Section 3.7, Backing Up and Restoring MySQL Cluster Manager Agents. (Bug #20070946) * Client: Warnings are now issued when users try to set internal options (options used only for internal testing) with the mcm client. (Bug #21253863) * Client: For configuration parameters of the enumeration type, when invalid values for them are set, mcm now include a list of valid values in the error message. (Bug #18502419) * Client: A warning message is now issued when the add package command is used to add to MySQL Cluster Manager a version of MySQL Cluster that has already been deprecated. (Bug #17894620) Bugs Fixed * Agent: A rolling restart of a cluster was timeouted when no events were received from a restarting data node for more than two minutes. (Bug #221287290) * Agent: During the recovery of a cluster, if the cluster's network configuration had been changed since it was last defined and a host could not be connected to, the recovery process would hang. With this fix, at the situation, a warning is written to the log of any agent that is unable to properly resolve host names of other agents of the site. (Bug #21169405) * Agent: After setting the parameter BackupDataDir for data nodes, if some of the data nodes were using the same backup directory, the list backups command would give wrong information on the backups. (Bug #21144638) * Agent: On Windows platforms, the backup of the agent configuration automatically created by mcmd during a cluster upgrade was inconsistent, with contents different from those in the original agent repository. (Bug #21135075) * Agent: When a mysqld node using a non-default location for its data directory was added to a already running cluster, trying to start the added node with the start process --added command resulted in a timeout error. (Bug #21111944) * Agent: A restore cluster command timed out when some nodes were holding onto ndpapi slots that they did not need, so that the node responsible for rebuilding the indexes could not have the free API slot it was waiting for. This fix makes sure that API slots are not needlessly occupied during the restore cluster process. (Bug #20956393) * Agent: After a cluster backup was completed, running the command show status --backup resulted in an "Unable to get backup status for cluster" error if the parameter NoOfReplica was set to "1." (Bug #20950494) * Agent: When the show status command was run on a cluster, mcmd tried to connect to and query a management node even if it was known to have stopped. On Windows platforms, the query took a long time to finish. This fix eliminated the unnecessary query for the stopped node. (Bug #20916482) * Agent: When using the import config command, loading of extra configuration files by using the !include or !includedir directives in a configuration file failed if there were extra spaces between the directives and the file paths that followed. This fix corrects the way white spaces are handled for those directives. (Bug #20888600) * Agent: A segmentation fault occurred for the import config command when a key = value pair in the configuration file had only spaces after the "=". This fix corrects the ways whitespace characters in key = value entries are handled during an import. (Bug #20871452) * Agent: During a stop cluster process, the mcmd agent hung after being unable to stop a mysqld node. With this fix, the stop cluster process timeouts in the situation, and mcmd will throw an error immediately when the next non-forced stop cluster command is attempted. (Bug #19805950) * Agent: If the configuration parameter LogDestination for a cluster is set to CONSOLE or SYSLOG, mcmd will not be able to detect if the ndb_mgmd node is running, or to scan the log from the ndb_mgmd node; however no error was thrown in that situation. With this fix, an error is thrown, with a message stating that the log has to go to a file. (Bug #13040093) * Client: When using the add process command after a create cluster --import command but before an import cluster command, the added processes got stuck in the "added" status even after the cluster import. This would later cause mcmd to crash due to an assertion failure when performing other cluster operations; sometimes, even the repository might get corrupted, making a cluster restart impossible. (Bug #20985984) 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-6.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, Sreedhar S
Subject
Views
Written By
Posted
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.