Movatterモバイル変換

upgrade cluster {--package=|-P }package_name [{--nodeid|-n }node_id_list] [--force|-f] [--retry|-L] [--set=attribute_assignment_list]cluster_namenode_id_list:node_id[,node_id[, ...]]attribute_assignment_list:attribute_assignment[,attribute_assignment][,...]attribute_assignment:attribute_name:process_name[=value]

This command upgrades the cluster namedcluster_name to the software packagepackage_name specified with the--package. It finishes an upgrade by performing a rolling restart for the cluster, in which data nodes are restarted with the--initial option to have their data file systems rebuilt.

The new package must be registered usingadd package before you can use it for an upgrade; otherwise,upgrade cluster fails with an error.

To use the command to perform an upgrade on a cluster, unless some special options are used (see explanations on the--force,--retry, and--nodeid options below), the cluster must be in thefully operational status (you can check that using the commandshow status--clustercluster_name). A cluster created for import cannot be upgraded until the import has been completed. SeeSection 5.4.1, “Thecreate cluster Command”, andSection 4.5, “Importing MySQL NDB Clusters into MySQL Cluster Manager”, for more information.

Supposemycluster is using MySQL NDB Cluster 8.0.34, and the binaries are registered with a package named8.0.34, as shown by thislist clusters command:

mcm> list clusters mysite;+-----------+---------+| Cluster   | Package |+-----------+---------+| mycluster | 8.0.34  |+-----------+---------+1 row in set (1.80 sec)

Now you wish to upgrademycluster to MySQL NDB Cluster. Assuming that you have placed the NDB 8.4.6 binaries in the same directory on each host, theadd package command to create a new package named8.4.6 that contains these binaries might look something like this:

mcm> add package --basedir=/usr/local/ndb-8.4.6 8.4.6;+----------------------------+| Command result             |+----------------------------+| Package added successfully |+----------------------------+1 row in set (0.88 sec)

Both packages should now be listed in the output of the commandlist packages mysite. To perform the upgrade to the8.4.6 package, use theupgrade cluster command as shown here:

mcm> upgrade cluster --package=8.4.6 mycluster;+--------------------------------------+| Command result                       |+--------------------------------------+| Cluster version changed successfully |+--------------------------------------+1 row in set (3 min 17.00 sec)

Once theupgrade cluster command has been successfully executed, you can verify thatmycluster is now using the8.4.6 package from the output of the appropriatelist clusters command:

mcm> list clusters mysite;+-----------+---------+| Cluster   | Package |+-----------+---------+| mycluster | 8.4.6  |+-----------+---------+1 row in set (1.80 sec)

The command can perform major as well as minor series upgrades. Despite the name of this command,upgrade cluster can also be used to perform MySQL NDB Cluster downgrades.

Not all upgrades and downgrades between different versions of MySQL NDB Cluster are supported by the command. These criteria must be met:

When using theupgrade cluster command, you can use the--set option to reconfigure your MySQL NDB Cluster at the same time. This is particularly helpful when the upgrade requires configuration changes to your cluster. This option takes as its argument an attribute assignment list similar in format to that used with theget andset commands; see description of theset command on the proper way to formulate an attribute assignment list. For example: if you want to change the memory assigned to each data node for storing database records to 750M, specify that with the--set option in yourupgrade cluster command:

mcm> upgrade cluster --package=8.4.6 --set=DataMemory:ndbd=750M  mycluster;+--------------------------------------+| Command result                       |+--------------------------------------+| Cluster version changed successfully |+--------------------------------------+1 row in set (3 min 17.04 sec)

Options for dealing with failed upgrades

The--force option (-f for short) should be used when you want to run theupgrade cluster command again after a failed upgrade attempt that ends up with any failed management or data nodes. Without the--force option, theupgrade cluster command only runs when the cluster is in thefully operational status.

The--retry option (-L for short) should be used when you want to retry theupgrade cluster command after a failed attempt that ends up with some nodes being upgraded, and some not. Without the--retry option, theupgrade cluster command cannot be run on the same cluster twice using the same package.

In the case of a failed or incomplete upgrade, instead of using the--force and--retry option, you can also choose to retry the upgrade only on the failed nodes by specifying them using the--nodeid option (-n in short). Check for any failed nodes after a failed upgrade:

mcm> upgrade cluster -P next mycluster;ERROR 7006 (00MGR): Process error: <reason of failure>mcm> show status --process mycluster;+--------+----------+----------+---------+-----------+-----------+| NodeId | Process  | Host     | Status  | Nodegroup | Package   |+--------+----------+----------+---------+-----------+-----------+| 49     | ndb_mgmd | thinkpad | running |           | next      || 1      | ndbmtd   | thinkpad | running | 0         | next      || 2      | ndbmtd   | thinkpad | running | 0         | next      || 50     | mysqld   | thinkpad | running |           | next      || 51     | mysqld   | thinkpad | failed  |           | next      || 52     | ndbapi   | *        | added   |           |           |+--------+----------+----------+---------+-----------+-----------+6 rows in set (0.03 sec)

Then, issue the command again, specifying the failed node with the--nodeid option:

mcm> upgrade cluster --nodeid=51 -P next mycluster;+--------------------------------------+| Command result                       |+--------------------------------------+| Cluster version changed successfully |+--------------------------------------+1 row in set (26.03 sec)