Skip navigation links

Additional languages
MySQL 5.1 Reference Manual :: 19 MySQL Cluster :: 19.17 Changes in MySQL Cluster 6.x :: 19.17.3 Changes in MySQL Cluster NDB 6.1 :: 19.17.3.13 Changes in MySQL Cluster NDB 6.1.11 (5.1.15-ndb-6.1.11) (06 June 2007)
19.17.3.14 Changes in MySQL Cluster NDB 6.1.10 (5.1.15-ndb-6.1.10) (30 May 2007) »
Section Navigation      [Toggle]

19.17.3.13. Changes in MySQL Cluster NDB 6.1.11 (5.1.15-ndb-6.1.11) (06 June 2007)

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 consider upgrading to MySQL Cluster NDB 6.2 or 6.3.

This Beta release incorporates all bugfixes and changes made in previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.15 (see Section C.1.13, “Changes in MySQL 5.1.15 (25 January 2007)”).

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:

  • Important Change: MySQL Cluster: The TimeBetweenWatchdogCheckInitial configuration parameter was added to allow setting of a separate watchdog timeout for memory allocation during startup of the data nodes. See Section 19.3.4.5, “Defining Data Nodes”, for more information. (Bug#28899)

  • MySQL Cluster: A new configuration parameter ODirect causes NDB to attempt using O_DIRECT writes for LCP, backups, and redo logs, often lowering CPU usage.

  • It is now possible to set the size of redo log files (fragment log files) using the FragmentLogFileSize configuration parameter.

Bugs fixed:

  • MySQL Cluster: Having large amounts of memory locked caused swapping to disk. (Bug#28751)

  • MySQL Cluster: LCP files were not removed following an initial system restart. (Bug#28726)

  • Disk Data: Repeated INSERT and DELETE operations on a Disk Data table having one or more large VARCHAR columns could cause data nodes to fail. (Bug#20612)