--bind-address

Causes ndbd to bind to a specific network interface. This option has no default value.

This option was added in MySQL 5.1.12.

--daemon, -d

Instructs ndbd to execute as a daemon process. This is the default behavior. --nodaemon can be used to prevent the process from running as a daemon.

--initial

Instructs ndbd to perform an initial start. An initial start erases any files created for recovery purposes by earlier instances of ndbd. It also re-creates recovery log files. Note that on some operating systems this process can take a substantial amount of time.

An --initial start is to be used only the very first time that the ndbd process is started because it removes all files from the Cluster filesystem and re-creates all REDO log files. The exceptions to this rule are:

This option does not affect either of the following:

It is possible to achieve the same effect by deleting by other means (such as using rm -r -f) all files and directories in the data node's DataDir — with the possible exception of the BACKUP directory in DataDir, should you wish to retain any backups that have been created on that data node — and then starting ndbd without having to use the --initial option. This may be useful when scripting Cluster administrative tasks.

--initial-start

This option is used when performing a partial initial start of the cluster. Each node should be started with this option, as well as --no-wait-nodes.

For example, suppose you have a 4-node cluster whose data nodes have the IDs 2, 3, 4, and 5, and you wish to perform a partial initial start using only nodes 2, 4, and 5 — that is, omitting node 3:

ndbd --ndbd-nodeid=2 --no-wait-nodes=3 --initial-start
ndbd --ndbd-nodeid=4 --no-wait-nodes=3 --initial-start
ndbd --ndbd-nodeid=5 --no-wait-nodes=3 --initial-start

This option was added in MySQL 5.1.9.

--nowait-nodes=node_id_1[, node_id_2[, ...]]

This option takes a list of data nodes which for which the cluster will not wait for before starting.

This can be used to start the cluster in a partitioned state. For example, to start the cluster with only half of the data nodes (nodes 2, 3, 4, and 5) running in a 4-node cluster, you can start each ndbd process with --nowait-nodes=3,5. In this case, the cluster starts as soon as nodes 2 and 4 connect, and does not wait StartPartitionedTimeout milliseconds for nodes 3 and 5 to connect as it would otherwise.

If you wanted to start up the same cluster as in the previous example without one ndbd — say, for example, that the host machine for node 3 has suffered a hardware failure — then start nodes 2, 4, and 5 with --no-wait-nodes=3. Then the cluster will start as soon as nodes 2, 4, and 5 connect and will not wait for node 3 to start.

This option was added in MySQL 5.1.9.

--nodaemon

Instructs ndbd not to start as a daemon process. This is useful when ndbd is being debugged and you want output to be redirected to the screen.

--nostart, -n

Instructs ndbd not to start automatically. When this option is used, ndbd connects to the management server, obtains configuration data from it, and initializes communication objects. However, it does not actually start the execution engine until specifically requested to do so by the management server. This can be accomplished by issuing the proper START command in the management client (see Section 15.7.2, “Commands in the MySQL Cluster Management Client”).