MySQL 8.0 Reference Manual Including MySQL NDB Cluster 8.0

22.4.4 ndb_mgmd — The NDB Cluster Management Server Daemon

The management server is the process that reads the cluster configuration file and distributes this information to all nodes in the cluster that request it. It also maintains a log of cluster activities. Management clients can connect to the management server and check the cluster's status.

The following table includes options that are specific to the NDB Cluster management server program ndb_mgmd. Additional descriptions follow the table. For options common to most NDB Cluster programs (including ndb_mgmd), see Section 22.4.31, “Options Common to NDB Cluster Programs — Options Common to NDB Cluster Programs”.

Table 22.281 Command-line options for the ndb_mgmd program

Format Description Added, Deprecated, or Removed

--bind-address=host

Local bind address

All NDB 8.0 releases

--config-cache[=TRUE|FALSE]

Enable the management server configuration cache; TRUE by default.

All NDB 8.0 releases

--config-file=file (>=),

-f (>=)

Specify the cluster configuration file; in NDB-6.4.0 and later, needs --reload or --initial to override configuration cache if present

All NDB 8.0 releases

--configdir=directory,

--config-dir=directory (>=7.0.8)

Specify the cluster management server's configuration cache directory

All NDB 8.0 releases

--daemon,

-d

Run ndb_mgmd in daemon mode (default)

All NDB 8.0 releases

--initial

Causes the management server reload its configuration data from the configuration file, bypassing the configuration cache

All NDB 8.0 releases

--install[=name]

Used to install the management server process as a Windows service. Does not apply on non-Windows platforms.

All NDB 8.0 releases

--interactive

Run ndb_mgmd in interactive mode (not officially supported in production; for testing purposes only)

All NDB 8.0 releases

--log-name=name

A name to use when writing messages applying to this node in the cluster log.

All NDB 8.0 releases

--mycnf

Read cluster configuration data from the my.cnf file

All NDB 8.0 releases

--no-nodeid-checks

Do not provide any node id checks

All NDB 8.0 releases

--nodaemon

Do not run ndb_mgmd as a daemon

All NDB 8.0 releases

--nowait-nodes=list

Do not wait for these management nodes when starting this management server. Also requires --ndb-nodeid to be used.

All NDB 8.0 releases

--print-full-config,

-P

Print full configuration and exit

All NDB 8.0 releases

--reload

Causes the management server to compare the configuration file with its configuration cache

All NDB 8.0 releases

--remove[=name]

Used to remove a management server process that was previously installed as a Windows service, optionally specifying the name of the service to be removed. Does not apply on non-Windows platforms.

All NDB 8.0 releases

--verbose,

-v

Write additional information to the log.

All NDB 8.0 releases


It is not strictly necessary to specify a connection string when starting the management server. However, if you are using more than one management server, a connection string should be provided and each node in the cluster should specify its node ID explicitly.

See Section 22.3.3.3, “NDB Cluster Connection Strings”, for information about using connection strings. Section 22.4.4, “ndb_mgmd — The NDB Cluster Management Server Daemon”, describes other options for ndb_mgmd.

The following files are created or used by ndb_mgmd in its starting directory, and are placed in the DataDir as specified in the config.ini configuration file. In the list that follows, node_id is the unique node identifier.