The table shown here provides information on MySQL Cluster upgrade and downgrade compatibility among different releases of MySQL 5.1 prior to MySQL 5.1.24. Additional notes about upgrades and downgrades to, from, or within the MySQL 5.1 release series can be found immediately following the table.
MySQL 5.1.3 was the first public release in this series.
Direct upgrades or downgrades between MySQL Cluster 5.0 and 5.1 are not supported; you must dump all
NDBCLUSTERtables using mysqldump, install the new version of the software, and then reload the tables from the dump.
You cannot downgrade a MySQL Cluster based on MySQL 5.1.6 or later and using Disk Data tables to MySQL 5.1.5 or earlier unless you convert all such tables to in-memory
MySQL 5.1.8, MySQL 5.1.10, and MySQL 5.1.13 were not released.
Online cluster upgrades and downgrades between MySQL 5.1.11 (or an earlier version) and 5.1.12 (or a later version) are not possible due to major changes in the cluster file system. In such cases, you must perform a backup or dump, upgrade (or downgrade) the software, start each data node with
--initial, and then restore from the backup or dump. You can use native
NDBbackup and restore, or mysqldump and
LOAD DATA INFILEfor this purpose.
Online downgrades from MySQL 5.1.14 or later to versions previous to 5.1.14 are not supported due to incompatible changes in the cluster system tables.
MySQL Cluster Replication: changes in ndb_apply_status.
Online upgrades from MySQL 5.1.17 and earlier to 5.1.18 and
later MySQL 5.1.x releases are not supported for clusters
using replication due to incompatible changes in the
mysql.ndb_apply_status table. (Online
upgrades from MySQL 5.1 to MySQL Cluster NDB 6.2 and later are
not supported, as discussed elsewhere in this section.)
However, it should not be necessary to shut down the cluster
entirely, if you follow this modified rolling restart
Stop the management server, update the management server software, then start the management server again. For multiple management servers, repeat this step for each management server in turn.
For each data node in turn: Stop the data node, update the data node daemon (in MySQL Cluster NDB 7.0 and later, this can be either ndbd or ndbmtd) with the new version, then restart the data node. It should not be necessary to use
--initialwhen restarting any of the data nodes after updating the software.
Stop all SQL nodes. Upgrade the existing MySQL server installations to the new version on all SQL nodes, then restart them. It is not necessary to start them one at a time after upgrading the MySQL server software, but there must be a time when none of them is running before starting any of them again using the 5.1.18 (or later) mysqld. Otherwise—due to the fact that
NDBstorage engine and is thus shared between all SQL nodes—there may be conflicts between the old and new versions of the table on different SQL nodes.
You can find more information about the changes to
ndb_apply_statusin Section 8.4, “MySQL Cluster Replication Schema and Tables”.
You should upgrade the MySQL Cluster software on each node using the same method by which it was originally installed. See Chapter 4, MySQL Cluster Installation and Upgrades, for more information.
As with any other MySQL Cluster version upgrade, you should also update the MySQL Cluster management client (ndb_mgm) and other MySQL Cluster client programs such as ndb_config and ndb_error_reporter; however, this does not have to be done in any particular order.
Internal column specification changes.
The internal specifications for columns in
NDBCLUSTER tables changed in
MySQL 5.1.18 to enable compatibility with later MySQL Cluster
releases that permit online adding and dropping of columns.
This change is not backward-compatible with earlier
To make tables created in MySQL 5.1.17 and earlier compatible with online adding and dropping of columns (available beginning with beginning with MySQL Cluster NDB 6.2.5 and MySQL Cluster NDB 6.3.2—see ALTER TABLE Syntax, for more information), it is necessary to force MySQL 5.1.18 and later to convert the tables to the new format by following this procedure:
Back up all
Upgrade the MySQL Cluster software on all data, management, and SQL nodes.
Shut down the cluster completely (this includes all data, management, and API or SQL nodes).
Restart the cluster, starting all data nodes with the
--initialoption (to clear and rebuild the data node file systems).
NDBCLUSTERtables from backup.
It is not necessary to follow this procedure for
NDBCLUSTER tables created in MySQL
5.1.18 and later; such tables are already compatible with online
adding and dropping of columns (as implemented beginning with
MySQL Cluster NDB 6.2.5 and MySQL Cluster NDB 6.3.2).
To minimize possible later difficulties, it is strongly advised that the procedure outlined above be followed as soon as possible after to upgrading from MySQL 5.1.17 or earlier to MySQL 5.1.18 or later.
Information about how this change effects users of MySQL Cluster NDB 6.x and 7.x is provided later in this section.
MySQL Cluster not supported in MySQL Server 5.1.24 and later. MySQL Cluster is not supported in standard MySQL 5.1 releases beginning with MySQL 5.1.24. If you are using MySQL Cluster in a standard MySQL 5.1 release, you should upgrade to the most recent MySQL Cluster NDB 7.0 or MySQL Cluster NDB 7.1 release.