|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Andrew Morgan (andrew.morgan
oracle.com)
Date: Thu May 02 2013 - 10:54:08 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dear MySQL users,
MySQL Cluster Manager 1.2.3 has been released and can be downloaded from https://support.oracle.com.
Documentation on using MySQL Cluster Manager can be found at http://dev.mysql.com/doc/mysql-cluster-manager/1.2/en/index.html and the release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster-manager/1.2/en/mcm-news-1-2-3.html
MySQL Cluster Manager offers three core capabilities to boost productivity and simplify administration
- Automated management
- Monitoring and self-healing recovery
- High availability operation
MySQL Cluster Manager is a part of the commercial MySQL Cluster Carrier Grade Edition database.
Andrew Morgan - MySQL High Availability Principal Product Manager.
andrew.morgan
oracle.com.
andrewmorgan.
www.clusterdb.com
=================
Functionality Added or Changed
==============================
Agent; Important Change: The default user name for MySQL Cluster Manager MySQL user accounts has been changed from admin to mcmd. See "Setting the MySQL Cluster Manager Agent User Name and Password" (http://dev.mysql.com/doc/cluster-manager/en/mcm-install-agent-user-password.html).
Client: The restore cluster command now supports restoring MySQL Cluster distributed privileges, using the --privilege-tables option added in this release. In addition, it is now possible to use IDs of SQL nodes as well as data nodes with the --skip-nodeid option.
Bugs Fixed
==========
Agent; Important Change: The default location for the agent data directory has been changed to /opt/mcm_data.
Agent; Important Change: MySQL Cluster Manager did not support many of the changes in, additions to, or removal of mysqld configuration attributes in MySQL Server 5.6 and MySQL Cluster NDB 7.3. The agent now knows about these changes. For information about these changes from MySQL 5.5 and MySQL Cluster NDB 7.2, see "What Is New in MySQL 5.6" (http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html).
Note
MySQL Cluster NDB 7.3.1 is currently available as a Developer Milestone
Release; for more information, see "MySQL Cluster NDB 7.3"
(http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster.html)
Agent: mcmd could fail to restart when the host system was restarted.
Agent: By default, the tmpdir for mysqld processes was set to datadir/tmp, which caused it to be treated as a database by the mysql client. Now the tmp directory in the MySQL installation directory is used by default.
Client: mcm client commands that failed due to the presence of extraneous characters following short options did so with no information about the cause. Now in such cases, a specific error message is issued in the client.
Client: The backup cluster command timed out when used with a cluster whose name contained exactly 8 bytes.
Client: The mcm client set command tried to handle values passed with the slave_skip_errors configuration attribute as wrong type (as booleans rather than strings), and failed.
--
MySQL Announce Mailing List
For list archives: http://lists.mysql.com/announce
To unsubscribe: http://lists.mysql.com/announce
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]