Upgrade and downgrade compatibility: MySQL 5.1

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.

Figure 17.7 MySQL Cluster Upgrade and Downgrade compatibility, MySQL Cluster 5.1

MySQL Cluster upgrade/downgrade compatibility, MySQL 5.1

Notes: MySQL 5.1

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 procedure:

  1. 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.

  2. 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 --initial when restarting any of the data nodes after updating the software.

  3. 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 mysql.ndb_apply_status uses the NDB storage 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_status in Section 17.6.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 Section 17.2, “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 MySQL versions.

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 Section 13.1.7, “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:

  1. Back up all NDBCLUSTER tables.

  2. Upgrade the MySQL Cluster software on all data, management, and SQL nodes.

  3. Shut down the cluster completely (this includes all data, management, and API or SQL nodes).

  4. Restart the cluster, starting all data nodes with the --initial option (to clear and rebuild the data node file systems).

  5. Restore the NDBCLUSTER tables 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.