Skip navigation links
MySQL 5.1 Reference Manual :: 17 MySQL Cluster NDB 6.X/7.X :: 17.7 Changes in MySQL Cluster NDB 6.X and 7.X :: 17.7.2 Changes in MySQL Cluster NDB 7.0 :: 17.7.2.5 Changes in MySQL Cluster NDB 7.0.12a (5.1.41-ndb-7.0.12a) (15 February 2010)
17.7.2.6 Changes in MySQL Cluster NDB 7.0.12 (5.1.41-ndb-7.0.12) (03 February 2010) »
Section Navigation      [Toggle]

17.7.2.5. Changes in MySQL Cluster NDB 7.0.12a (5.1.41-ndb-7.0.12a) (15 February 2010)

Note

MySQL Cluster NDB 7.0.12a was withdrawn shortly after release, due to Bug#51256. Users of the original 7.0.12 release should upgrade to MySQL Cluster NDB 7.0.12b, which fixes this issue (and others). Users of MySQL Cluster NDB 7.0.11 or MySQL Cluster NDB 7.0.11a should upgrade to MySQL Cluster NDB 7.0.11b, if they have not done so already.

This is a replacement release for MySQL Cluster NDB 7.0.12, fixing a critical issue in that version that was discovered shortly after its release (Bug#51027). MySQL Cluster NDB 7.0.12a is identical in all other respects to MySQL Cluster NDB 7.0.12. Users of MySQL Cluster NDB 7.0.12 (only) should upgrade to the 7.0.12a release as soon as possible.

This is a testing release only, for the purpose of testing the fix for Bug#49190 (now also incorporating the fix for Bug#51027). This release is otherwise identical to MySQL Cluster NDB 7.0.11b; users of MySQL Cluster NDB 7.0.11 or MySQL Cluster NDB 7.0.11a who are not interested in testing this change should upgrade to MySQL Cluster NDB 7.0.11b (if they have not done so already), then wait until MySQL Cluster NDB 7.0.13 becomes available.

This release incorporates all bugfixes and changes made in previous MySQL Cluster NDB 7.0 releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.41 (see Section C.1.7, “Changes in MySQL 5.1.41 (05 November 2009)”).

Note

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

Bugs fixed:

  • An initial restart of a data node configured with a large amount of memory could fail with a Pointer too large error. (Bug#51027)

    This regression was introduced by Bug#47818.