Documentation Home
MySQL NDB Cluster 6.1 - 7.1 Release Notes
Download these Release Notes
PDF (US Ltr) - 3.0Mb
PDF (A4) - 3.0Mb
EPUB - 0.6Mb


MySQL NDB Cluster 6.1 - 7.1 Release Notes  /  Changes in MySQL Cluster NDB 6.1  /  Changes in MySQL Cluster NDB 6.1.5 (5.1.15-ndb-6.1.5) (2007-03-15)

Changes in MySQL Cluster NDB 6.1.5 (5.1.15-ndb-6.1.5) (2007-03-15)

This is a bugfix release, fixing recently discovered bugs in the previous MySQL Cluster NDB 6.1 release.

MySQL Cluster NDB 6.1 no longer in development.  MySQL Cluster NDB 6.1 (formerly known as MySQL Cluster Carrier Grade Edition 6.1.x) is no longer being developed or maintained; if you are using a MySQL Cluster NDB 6.1 release, you should upgrade to the latest version of MySQL Cluster, which is available from http://dev.mysql.com/downloads/cluster/ .

This Beta release incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.15 (see Changes in MySQL 5.1.15 (2007-01-25)).

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

  • Incompatible Change; Cluster Replication: The schema for the ndb_apply_status table in the mysql system database has changed. When upgrading to this release from a previous MySQL Cluster NDB 6.x or mainline MySQL 5.1 release, you must drop the mysql.ndb_apply_status table, then restart the server for the table to be re-created with the new schema.

    See MySQL Cluster Replication Schema and Tables, for additional information.

Bugs Fixed

  • Creating a table on one SQL node while in single user mode caused other SQL nodes to crash. (Bug #26997)

  • mysqld processes would sometimes crash under high load.

    Note

    This fix was reverted in MySQL Cluster NDB 6.1.6.

    (Bug #26825)

  • An infinite loop in an internal logging function could cause trace logs to fill up with Unknown Signal type error messages and thus grow to unreasonable sizes. (Bug #26720)

  • Disk Data: When creating a log file group, setting INITIAL_SIZE to less than UNDO_BUFFER_SIZE caused data nodes to crash. (Bug #25743)