This is a bugfix release, fixing recently discovered bugs in the previous MySQL Cluster NDB 6.2 release.
Obtaining MySQL Cluster NDB 6.2. You can download the latest MySQL Cluster NDB 6.2 source code and binaries for supported platforms from http://dev.mysql.com/downloads/select.php?id=14.
This Beta release incorporates all bugfixes and changes made in previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.22 (see Section C.1.30, “Changes in MySQL 5.1.22 (24 September 2007 Release Candidate)”).
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:
The following improvements have been made in the ndb_size.pl utility:
The script can now be used with multiple databases; lists of databases and tables can also be excluded from analysis.
Schema name information has been added to index table calculations.
The database name is now an optional parameter, the exclusion of which causes all databases to be examined.
If selecting from
fails, the script now attempts to fall back to
--real_table_name option has been added;
this designates a table to handle unique index size
The report title has been amended to cover cases where more than one database is being analyzed.
Support for a
--socket option was also added.
For more information, see Section 17.4.21, “ndb_size.pl — NDBCLUSTER Size Requirement Estimator”. (Bug#28683, Bug#28253)
operations can now be performed explicitly for
NDB tables, as well as online
renaming of tables and columns for
tables — that is, without copying or locking of the
affected tables — using
You can force operations that would otherwise be performed
online to be done offline using the
It is now possible to control whether fixed-width or
variable-width storage is used for a given column of an
NDB table by means of the
COLUMN_FORMAT specifier as part of the
column's definition in a
It is also possible to control whether a given column of an
NDB table is stored in memory or on
disk, using the
STORAGE specifier as part of
the column's definition in a
For permitted values and other information about
see Section 12.1.17, “
CREATE TABLE Syntax”.
A new cluster management server startup option
--bind-address makes it possible
to restrict management client connections to
ndb_mgmd to a single host and port. For more
Section 17.4.4, “ndb_mgmd — The MySQL Cluster Management Server Daemon”.
The protocol for handling global checkpoints has been changed.
It is now possible to control how often the GCI number is
updated, and how often global checkpoints are written to disk,
parameter. This improves the reliability and performance of
MySQL Cluster Replication.
GCPs handled using the new protocol are sometimes referred to as “micro-GCPs”.
For more information, see
NDB tables did not
work correctly with
A file system close operation could fail during a node or system restart. (Bug#30646)
When creating an
NDB table with a column that
COLUMN_FORMAT = DYNAMIC, but the table
ROW_FORMAT=FIXED, the table is
considered dynamic, but any columns for which the row format is
unspecified default to
FIXED. Now in such
cases the server issues the warning Row format FIXED
incompatible with dynamic attribute
See also Bug#31482.
A query using joins between several large tables and requiring
unique index lookups failed to complete, eventually returning
Uknown Error after a very long period of
time. This occurred due to inadequate handling of instances
where the Transaction Coordinator ran out of
TransactionBufferMemory, when the cluster
should have returned NDB error code 4012 (Request
An attempt to perform a
SELECT ... FROM
INFORMATION_SCHEMA.TABLES whose result included
NDB tables for
which the user had no privileges crashed the MySQL Server on
which the query was performed.
An issue with the
table could cause
autodiscovery to fail in certain rare circumstances.
A call to
mgmapi.cpp should have been a call to