List:Announcements« Previous MessageNext Message »
From:Andrew Morgan Date:June 18 2013 5:03pm
Subject:MySQL Cluster 7.2.13 has been released
View as plain text  
Dear MySQL users,

MySQL Cluster 7.2.13, has been released and can be downloaded from
http://www.mysql.com/downloads/cluster/ - where you will also find "Quick Start" guides
to help you get your first MySQL Cluster database up and running. 

The release notes are available from
http://dev.mysql.com/doc/relnotes/mysql-cluster/7.2/en/mysql-cluster-news-5-5-31-ndb-7-2-13.html
MySQL Cluster enables users to meet the database challenges of next generation web, cloud,
and communications services with uncompromising scalability, uptime and agility. More
details can be found at http://www.mysql.com/products/cluster/ 

----------------------------------

#Functionality Added or Changed

- Cluster API: Added DUMP code 2514, which provides information about counts of
transaction objects per API node. For more information, see [DUMP
2514](http://dev.mysql.com/doc/ndbapi/en/ndb-internals-dump-command-2514.html). See also
[Commands in the MySQL Cluster Management
Client](http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-mgm-client-commands.html).
(Bug #15878085)

- When ndb_restore fails to find a table, it now includes in the error output an NDB API
error code giving the reason for the failure. (Bug #16329067)

#Bugs Fixed

- Incompatible Change; Cluster Replication: The default value for the
[binlog_format](http://dev.mysql.com/doc/refman/5.5/en/replication-options-binary-log.html#sysvar_binlog_format)
system variable when the [NDB](http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster.html)
storage engine is enabled is now MIXED. If NDB is not enabled, the default binary logging
format is STATEMENT, as in the standard MySQL Server. (Bug #16417224)

- (Bug #16765651)

- The NDB Error-Reporting Utility (ndb_error_reporter) failed to include the cluster
nodes' log files in the archive it produced when the FILE option was set for the
parameter
[LogDestination](http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-mgm-definition.html#ndbparam-mgmd-logdestination).
(Bug #16765651)

- A WHERE condition that contained a boolean test of the result of an IN subselect was not
evaluated correctly. (Bug #16678033)

- In some cases a data node could stop with an exit code but no error message other than
(null) was logged. (This could occur when using ndbd or ndbmtd for the data node
process.) Now in such cases the appropriate error message is used instead (see [ndbd
Error Messages](http://dev.mysql.com/doc/ndbapi/en/ndbd-error-messages.html)). (Bug
#16614114)

- Improved handling of lagging row change event subscribers by setting size of the GCP
pool to the value of
[MaxBufferedEpochs](http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbd-maxbufferedepochs).
This fix also introduces a new
[MaxBufferedEpochBytes](http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbd-maxbufferedepochbytes)
data node configuration parameter, which makes it possible to set a total number of bytes
per node to be reserved for buffering epochs. In addition, a new DUMP code (8013) has
been added which causes a list a lagging subscribers for each node to be printed to the
cluster log (see [DUMP
8013](http://dev.mysql.com/doc/ndbapi/en/ndb-internals-dump-command-8013.html)). (Bug
#16203623)

- Purging the binary logs could sometimes cause mysqld to crash. (Bug #15854719)

- An error message in src/mgmsrv/MgmtSrvr.cpp was corrected. (Bug #14548052, Bug #66518)

- The help text for ndb_select_count did not include any information about using table
names. (Bug #11755737, Bug #47551)

----------------------------------

Best Regards, Andrew Morgan.

MySQL High Availability Principal Product Manager.
andrew.morgan@stripped .
@andrewmorgan .
www.clusterdb.com .
Thread
MySQL Cluster 7.2.13 has been releasedAndrew Morgan18 Jun