Oracle 5.0 Reference Manual page 1643

To start ndbd, it may also be necessary to specify the host name of the management server and the
port on which it is listening. Optionally, one may also specify the node ID that the process is to use.
shell> ndbd --connect-string="nodeid=2;host=ndb_mgmd.mysql.com:1186"
See Section 17.3.2.2, "The MySQL Cluster
Section 17.4.1,
When
ndbd
only job is to discover when the execution process has been completed, and then to restart the
process if it is configured to do so. Thus, if you attempt to kill
it is necessary to kill both processes, beginning with the angel process. The preferred method of
terminating an
The execution process uses one thread for reading, writing, and scanning data, as well as all other
activities. This thread is implemented asynchronously so that it can easily handle thousands of
concurrent actions. In addition, a watch-dog thread supervises the execution thread to make sure that
it does not hang in an endless loop. A pool of threads handles file I/O, with each thread able to handle
one open file. Threads can also be used for transporter connections by the transporters in the
process. In a multi-processor system performing a large number of operations (including updates), the
process can consume up to 2 CPUs if permitted to do so.
ndbd
For a machine with many CPUs it is possible to use several
node groups; however, such a configuration is still considered experimental and is not supported for
MySQL 5.0 in a production setting. See
17.4.2.
ndb_mgmd
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 MySQL Cluster management server
program ndb_mgmd. Additional descriptions follow the table. For options common to most MySQL
Cluster programs (including ndb_mgmd), see
Programs — Options Common to MySQL Cluster
Table 17.10.
Format
--config-file=file
-f [1624],
-c [1624]
--print-full-config
-P [1625]
--daemon
-d [1624]
--nodaemon [1625]
--interactive [1624]
--no-nodeid-checks [1624]
— The MySQL Cluster Management Server Daemon
ndb_mgmd
"ndbd — The MySQL Cluster Data Node
starts, it actually initiates two processes. The first of these is called the "angel process"; its
process is to use the management client and stop the process from there.
ndbd
— The MySQL Cluster Management Server Daemon
Options and Variables: MySQL 5.0
ndb_mgmd
[1624],
[1625],
[1624],
Connectstring", for additional information about this issue.
Daemon", describes other options for ndbd.
ndbd
ndbd
Section 17.1.5, "Known Limitations of MySQL
Section 17.4.20, "Options Common to MySQL Cluster
Programs".
Description
Specify the cluster configuration
file; in NDB-6.4.0 and later, needs
--reload or --initial to override
configuration cache if present
Print full configuration and exit
Run ndb_mgmd in daemon mode
(default)
Do not run ndb_mgmd as a
daemon
Run ndb_mgmd in interactive
mode (not officially supported in
production; for testing purposes
only)
Do not provide any node id checks All MySQL 5.0
1623
using the Unix command,
kill
processes which belong to different
Cluster".
Added / Removed
All MySQL 5.0
based releases
ADDED: 5.0.10
All MySQL 5.0
based releases
All MySQL 5.0
based releases
All MySQL 5.0
based releases
based releases
ndbd
ndbd