Skip navigation links

Additional languages
MySQL 5.1 Reference Manual :: 16 MySQL Cluster :: 16.17 Changes in MySQL Cluster 6.x :: 16.17.1 Changes in MySQL Cluster NDB 6.3 :: 16.17.1.4 Changes in MySQL Cluster NDB 6.3.16 (5.1.24-ndb-6.3.16) (27 June 2008)
16.17.1.5 Changes in MySQL Cluster NDB 6.3.15 (5.1.24-ndb-6.3.15) (30 May 2008) »
Section Navigation      [Toggle]

16.17.1.4. Changes in MySQL Cluster NDB 6.3.16 (5.1.24-ndb-6.3.16) (27 June 2008)

This is a new source release, fixing recently discovered bugs in previous MySQL Cluster NDB 6.3 releases.

Obtaining MySQL Cluster NDB 6.3.  MySQL Cluster NDB 6.3 releases are source-only releases which you must compile and install using the instructions found in Section 2.9, “MySQL Installation Using a Source Distribution”, and in Section 16.3.1, “Building MySQL Cluster from Source Code”. You can download the GPL source tarball from the MySQL FTP site at ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/.

This release incorporates all bugfixes and changes made in the previous MySQL Cluster NDB 6.3 release, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.24 (see Section C.1.6, “Changes in MySQL 5.1.24 (08 April 2008)”).

Note

Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.

Functionality added or changed:

  • MySQL Cluster: Event buffer lag reports are now written to the cluster log. (Bug#37427)

  • MySQL Cluster: Added the --no-binlog option for ndb_restore. When used, this option prevents information being written to SQL node binary logs from the restoration of a cluster backup. (Bug#30452)

Bugs fixed:

  • Cluster API: MySQL Cluster: Changing the system time on data nodes could cause MGM API applications to hang and the data nodes to crash. (Bug#35607)

  • MySQL Cluster: Failure of a data node could sometimes cause mysqld to crash. (Bug#37628)

  • MySQL Cluster: DELETE ... WHERE unique_index_column=value deleted the wrong row from the table. (Bug#37516)

  • MySQL Cluster: If subscription was terminated while a node was down, the epoch was not properly acknowledged by that node. (Bug#37442)

  • MySQL Cluster: libmysqld failed to wait for the cluster binlog thread to terminate before exiting. (Bug#37429)

  • MySQL Cluster: In rare circumstances, a connection followed by a disconnection could give rise to a “stale” connection where the connection still existed but was not seen by the transporter. (Bug#37338)

  • MySQL Cluster: Queries against NDBCLUSTER tables were cached only if AUTOCOMMIT was in use. (Bug#36692)

  • Cluster Replication: Data was written to the binlog with --log-slave-updates disabled. (Bug#37472)

  • Cluster API: Creating a table on an SQL node, then starting an NDB API application that listened for events from this table, then dropping the table from an SQL node, prevented data node restarts. (Bug#37279)

  • Cluster API: When some operations succeeded and some failed following a call to NdbTransaction::execute(Commit, AO_IgnoreOnError), a race condition could cause spurious occurrences of NDB API Error 4011 (Internal error). (Bug#37158)

  • Cluster API: A buffer overrun in NdbBlob::setValue() caused erroneous results on Mac OS X. (Bug#31284)