3.7.1 Upgrading and Downgrading NDB 7.5

This section provides information about compatibility between different NDB Cluster 7.5 releases with regard to performing upgrades and downgrades as well as compatibility matrices and notes. Additional information can also be found here regarding downgrades from NDB 7.5 to previous NDB release series. You should already be familiar with installing and configuring NDB Cluster prior to attempting an upgrade or downgrade. See Chapter 4, Configuration of NDB Cluster.

The table shown here provides information on NDB Cluster upgrade and downgrade compatibility among different releases of NDB 7.5. Additional notes about upgrades and downgrades to, from, or within the NDB Cluster 7.5 release series can be found following the table.

Figure 3.2 NDB Cluster Upgrade and Downgrade Compatibility, MySQL NDB Cluster 7.5

Version support.  The following versions of NDB Cluster are supported for upgrades to GA releases of NDB Cluster 7.5 (7.5.4 and later):

• NDB Cluster 7.4 GA releases (7.4.4 and later)

• NDB Cluster 7.3 GA releases (7.3.2 and later)

Known Issues When Upgrading or Downgrading NDB Cluster 7.5.  The following issues are known to occur when upgrading to or between NDB 7.5 releases:

• When run with --initialize, the server does not require NDB support; having NDB enabled at this time can cause problems with ndbinfo tables. To keep this from happening, the --initialize option now causes mysqld to ignore the --ndbcluster option if the latter is also specified.

  A workaround for an upgrade that has failed for these reasons can be accomplished as follows:

  1. Perform a rolling restart of the entire cluster

  2. Delete all .frm files in the data/ndbinfo directory

  3. Run mysql_upgrade.

  (Bug #81689, Bug #82724, Bug #24521927, Bug #23518923)

• During an online upgrade from an NDB Cluster 7.3 release to an NDB 7.4 (or later) release, the failures of several data nodes running the lower version during local checkpoints (LCPs), and just prior to upgrading these nodes, led to additional node failures following the upgrade. This was due to lingering elements of the EMPTY_LCP protocol initiated by the older nodes as part of an LCP-plus-restart sequence, and which is no longer used in NDB 7.4 and later due to LCP optimizations implemented in those versions. This issue was fixed in NDB 7.5.4. (Bug #23129433)

• In NDB 7.5 (and later), the ndb_binlog_index table uses the InnoDB storage engine. Use of the MyISAM storage engine for this table continues to be supported for backward compatibility.

  When upgrading a previous release to NDB 7.5 (or later), you can use the --force --upgrade-system-tables options with mysql_upgrade so that it performs ALTER TABLE ... ENGINE=INNODB on the ndb_binlog_index table.

  For more information, see Section 7.4, “NDB Cluster Replication Schema and Tables”.