4.8.2 The import config Command

import config [--dryrun|-y] cluster_name

This command imports the configuration of an autonomous or “wild” cluster into the cluster named cluster_name.

import config requires a single argument, cluster_name, which is the name of the cluster created using MySQL Cluster Manager into which you wish to import the configuration of a MySQL NDB Cluster created externally. The cluster named in the command must already exist in MySQL Cluster Manager; you are also strongly advised to use create cluster --import when creating cluster_name.

import config also supports a --dryrun option (short form: -y). When this option is used, the checks required for importing the configuration data are performed, and the set commands for performing the actual import are written to the file /path-to-mcm-data-repository/clusters/clustername/tmp/import_config.message_id.mcm for your examination. This makes it possible to test the configuration import without actually copying any of the settings into the cluster controlled by MySQL Cluster Manager. You can then import all the settings using the import config command (without the --dryrun option), or adjust some of the settings in the /path-to-mcm-data-repository/clusters/clustername/tmp/import_config.message_id.mcm file and then import the settings by executing the file with the mcm agent. See Section 3.5.2.3, “Creating and Configuring the Target Cluster” for examples on using the import config command.

Note

When importing configuration attributes for a mysqld node, if a relative path is used for the socket value or for any directory value (for example, plugin_dir), the import will be rejected by the mcm client. Make sure an absolute path is used in those cases and, if necessary, make adjustments to the attributes in the .mcm file produced by the import config --dryrun command and then import the settings by executing the file with the mcm client.