Movatterモバイル変換

To start the MySQL Cluster Manager agent manually on a Windows host, you should invokemcmd.exe, found in thebin directory under the manager installation directory on that host. If the configuration file's location is not specified with the--config option, mcmd looks for the file at its default locations (seeSection 3.4, “MySQL Cluster Manager Configuration File” for details).

Typical options formcmd are shown here:

mcmd[.exe] [--config=filename | --bootstrap]

For information about additional options that can be used withmcmd on the command line or in an option file, seeSection 4.1, “mcmd, the MySQL Cluster Manager Agent”.

By default, the agent assumes that the agent configuration file ismcmd.conf in the MySQL Cluster Manager installation directory (seeSection 3.4, “MySQL Cluster Manager Configuration File” for more details). You can tell the agent to use a different configuration file by passing the path to this file to the--config option, as shown here:

C:\Program Files (x86)\MySQL\MySQL Cluster Manager 9.5.0\bin>  mcmd --config="C:\Program Files (x86)\MySQL\MySQL Cluster Manager 9.5.0\etc\mcmd.ini"

The--bootstrap option causes the agent to start with default configuration values, create a default one-machine cluster namedmycluster, and start it. The use of this option withmcmd is shown here on a system having the host nametorsk, where MySQL Cluster Manager has been installed to the default location:

C:\Program Files\MySQL\MySQL Cluster Manager 9.5.0\bin>mcmd --bootstrapMySQL Cluster Manager 9.5.0 startedConnect to MySQL Cluster Manager by running "C:\Program Files\MySQL\MySQL Cluster Manager 9.5.0\bin\mcm" -h TORSK -P 1862Configuring default cluster 'mycluster'...Starting default cluster 'mycluster'...Cluster 'mycluster' started successfully        ndb_mgmd        TORSK:1186        ndbd            TORSK        ndbd            TORSK        mysqld          TORSK:3306        mysqld          TORSK:3307        ndbapi          *Connect to the database by running "C:\Program Files\MySQL\MySQL Cluster Manager 9.5.0\cluster\bin\mysql" -h TORSK -P 3306 -u root

You can then connect to the agent using themcm client (seeSection 4.3, “Starting the MySQL Cluster Manager Client”), and to either of the MySQL Servers running on ports 3306 and 3307 usingmysql or another MySQL client application.

When starting the MySQL Cluster Manager agent for the first time, you may see one or more WindowsSecurity Alert dialogs. You should grant permission to connect to private networks for any of the programsmcmd.exe,ndb_mgmd.exe,ndbd.exe,ndbmtd.exe, ormysqld.exe. To do so, check thePrivate Networks... box and then click theAllow access button. It is generally not necessary to grant MySQL Cluster Manager or MySQL NDB Cluster access to public networks such as the Internet.

SeeSection 4.1, “mcmd, the MySQL Cluster Manager Agent”, for more information about options that can be used withmcmd.

The MySQL Cluster Manager agent must be started on each host in the MySQL NDB Cluster to be managed.

It is possible to install MySQL Cluster Manager as a Windows service, so that it is started automatically each time Windows starts. SeeSection 3.3.2.1, “Installing the MySQL Cluster Manager Agent as a Windows Service”.

To stop one or more instances of the MySQL Cluster Manager agent, use thestop agents command in the MySQL Cluster Manager client. You can also stop an agent process using the Windows Task Manager. In addition, if you have installed MySQL Cluster Manager as a Windows service, you can stop (and start) the agent using the Windows Service Manager,CTRL-C, or the appropriateSC STOP (orSC START) orNET STOP (orNET START) command. SeeStarting and stopping the MySQL Cluster Manager agent Windows service, for more information about each of these options.