upgrade cluster {--package=|-P }package_name cluster_name
This command upgrades the cluster named
cluster_name to the software package
package_name. If the cluster is
running, then upgrade cluster accomplishes
this by performing a rolling restart of the cluster.
The new package must be registered using add
package before you can use it for an upgrade;
otherwise, upgrade cluster fails with an
error.
For example, suppose mycluster is using MySQL
Cluster NDB 7.1.17, and the binaries are registered with a
package named 7.1.17, as shown by this
list clusters command:
mcm> list clusters mysite;
+-----------+---------+
| Cluster | Package |
+-----------+---------+
| mycluster | 7.1.17 |
+-----------+---------+
1 row in set (1.80 sec)
Now you wish to upgrade mycluster to MySQL
Cluster NDB 7.1.19. Assuming that you have placed the NDB 7.1.19
binaries in the same directory on each host, the add
package command to create a new package named
7.1.19 that contains these binaries might
look something like this:
mcm> add package --basedir=/usr/local/ndb-7.1.19 7.1.19;
+----------------------------+
| Command result |
+----------------------------+
| Package added successfully |
+----------------------------+
1 row in set (0.88 sec)
On Windows, you must replace any backslash
(\) characters in the path used for the
add package command's
--basedir option with forward slashes
(/). See Section 3.3.1, “The add package Command”,
for additional information and examples.
Both packages should now be listed in the output of the command
list packages mysite. To perform the upgrade
to the 7.1.19 package, use the
upgrade cluster command as shown here:
mcm> upgrade cluster --package=7.1.19 mycluster;
+-------------------------------+
| Command result |
+-------------------------------+
| Cluster upgraded successfully |
+-------------------------------+
1 row in set (3 min 17.00 sec)
Once the upgrade cluster command has been
successfully executed, you can verify that
mycluster is now using the
7.1.19 package from the output of the
appropriate list clusters command:
mcm> list clusters mysite;
+-----------+---------+
| Cluster | Package |
+-----------+---------+
| mycluster | 7.1.19 |
+-----------+---------+
1 row in set (1.80 sec)
Despite the name of this command, upgrade
cluster can also be used to perform MySQL Cluster
downgrades.
MySQL Cluster Manager does not allow cluster upgrades or downgrades not
supported by MySQL Cluster. Before attempting any upgrade or
downgrade using the upgrade cluster command,
be sure to consult
Upgrading and Downgrading MySQL Cluster, to determine
whether MySQL Cluster supports the upgrade or downgrade in
question, and for any known issues regarding the changes you
intend to make.
