This section provides information about NDB Cluster software and table file compatibility between different NDB Cluster 7.5 releases with regard to performing upgrades and downgrades as well as compatibility matrices and notes. You are expected already to be familiar with installing and configuring an NDB Cluster prior to attempting an upgrade or downgrade. See Section 21.3, “Configuration of NDB Cluster”.
Only compatibility between MySQL versions with regard to
NDBCLUSTER is taken into account in
this section, and there are likely other issues to be
considered. As with any other MySQL software upgrade
or downgrade, you are strongly encouraged to review the relevant
portions of the MySQL Manual for the MySQL versions from which
and to which you intend to migrate, before attempting an upgrade
or downgrade of the NDB Cluster software. See
Section 2.11, “Upgrading MySQL”.
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.
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)
NDB Cluster 7.2 GA releases (7.2.4 and later)
Known Issues - NDB 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
NDBenabled at this time can cause problems with
ndbinfotables. To keep this from happening, the
--initializeoption now causes mysqld to ignore the
--ndbclusteroption if the latter is also specified.
A workaround for an upgrade that has failed for these reasons can be accomplished as follows:
Perform a rolling restart of the entire cluster
.frmfiles in the
(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_LCPprotocol 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)
Beginning with NDB 7.5.2, the
ndb_binlog_indextable uses the
InnoDBstorage engine. (Use of the
MyISAMstorage engine for this table continues to be supported for backward compatibility.)
When upgrading a previous release to NDB 7.5.2 or later, you can use the
--upgrade-system-tablesoptions with mysql_upgrade so that it performs
ALTER TABLE ... ENGINE=INNODBon the
For more information, see Section 21.6.4, “NDB Cluster Replication Schema and Tables”.
Online upgrades from previous versions of NDB Cluster to NDB 7.5.1 were not possible due to missing entries in the matrix used to test upgrade compatibility between versions. (Bug #22024947)
Also in NDB 7.5.1, mysql_upgrade failed to upgrade the
sysschema if a
sysdatabase directory existed but was empty. (Bug #81352, Bug #23249846, Bug #22875519)
Known issues - NDB 7.6. The following issues are known to occur when upgrading to or between NDB 7.6 releases:
Changes in Disk Data file format. Due to changes in disk format, upgrading to or downgrading from either of the versions listed here requires an initial node restart of each data node:
To avoid problems relating to the old format, you should re-create
any existing tablespaces and undo log file groups when upgrading.
You can do this by performing an initial restart of each data node
(that is, using the
as part of the upgrade process.
If you are using Disk Data tables, a downgrade from
any NDB 7.6 release to any NDB 7.5 or earlier
release requires that you restart all data nodes with
--initial as part of the downgrade
process. This is because NDB 7.5 and earlier release series are
not able to read the new Disk Data file format.
Upgrading to NDB 7.6.4 or later from an earlier release, or
downgrading from NDB 7.6.4 or later to an earlier release,
requires purging then re-creating the
data node file system, which means that each data node must be
restarted using the
option as part of the rolling restart or system restart normally
required. (Starting a data node with no file system is already
equivalent to an initial restart; in such cases,
--initial is implied and not required. This is
unchanged from previous releases of NDB Cluster.)
When such a restart is performed as part of an upgrade to NDB
7.6.4 or later, any existing LCP files are checked for the
presence of the LCP
sysfile, indicating that
the existing data node file system was written using NDB 7.6.4
or later. If such a node file system exists, but does not
sysfile, and if any data nodes
are restarted without the
NDB causes the restart to fail with
an appropriate error message.
You should also be aware that no such protection is possible when downgrading from NDB 7.6.4 or later to a release previous to to NDB 7.6.4.