t
 Title: ndbd
 Author: [FIXME: author] [see http://docbook.sf.net/el/author]
 Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
 Date: 06/07/2021
 Manual: MySQL Database System
 Source: MySQL 5.7
 Language: English

 "NDBD" "8" "06/07/2021" "MySQL 5.7" "MySQL Database System"
 -----------------------------------------------------------------
 * Define some portability stuff
 -----------------------------------------------------------------
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 http://bugs.debian.org/507673
 http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 -----------------------------------------------------------------
 * set default formatting
 -----------------------------------------------------------------
 disable hyphenation
 disable justification (adjust text to left margin only)
 -----------------------------------------------------------------
 * MAIN CONTENT STARTS HERE *
 -----------------------------------------------------------------
 "NAME"
ndbd - the NDB Cluster data node daemon

 "SYNOPSIS"
 \w'ndbd options 'u
ndbd options

 "DESCRIPTION"

ndbd
is the process that is used to handle all the data in tables using the NDB Cluster storage engine. This is the process that empowers a data node to accomplish distributed transaction handling, node recovery, checkpointing to disk, online backup, and related tasks.


In an NDB Cluster, a set of
ndbd
processes cooperate in handling data. These processes can execute on the same computer (host) or on different computers. The correspondences between data nodes and Cluster hosts is completely configurable.


Options that can be used with
ndbd
are shown in the following table. Additional descriptions follow the table.
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1


 Table 21.22. Command-line options used with the program ndbd 



Format
:
Description
:
Added, Deprecated, or Removed
.T&
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l
lB l l.
 --bind-address=name 
:
Local bind address
:
(Supported in all NDB releases based on MySQL 5.7)
 --character-sets-dir=path 
:
Directory containing character sets
:
(Supported in all NDB releases based on MySQL 5.7)
 --connect-delay=# 
:
Time to wait between attempts to contact a management server, in
 seconds; 0 means do not wait between attempts
:
(Supported in all NDB releases based on MySQL 5.7)
 --connect-retries=# 
:
Set the number of times to retry a connection before giving up; 0 means
 1 attempt only (and no retries)
:
(Supported in all NDB releases based on MySQL 5.7)
 --connect-retry-delay=# 
:
Time to wait between attempts to contact a management server, in
 seconds; 0 means do not wait between attempts
:
(Supported in all NDB releases based on MySQL 5.7)
--connect-string=connection-string,
 -c 
:
Same as --ndb-connectstring
:
(Supported in all NDB releases based on MySQL 5.7)
 --core-file 
:
Write core file on error; used in debugging
:
(Supported in all NDB releases based on MySQL 5.7)
--daemon,
 -d 
:
Start ndbd as daemon (default); override with --nodaemon
:
(Supported in all NDB releases based on MySQL 5.7)
 --defaults-extra-file=path 
:
Read given file after global files are read
:
(Supported in all NDB releases based on MySQL 5.7)
 --defaults-file=path 
:
Read default options from given file only
:
(Supported in all NDB releases based on MySQL 5.7)
 --defaults-group-suffix=string 
:
Also read groups with concat(group, suffix)
:
(Supported in all NDB releases based on MySQL 5.7)
 --foreground 
:
Run ndbd in foreground, provided for debugging purposes (implies
 --nodaemon)
:
(Supported in all NDB releases based on MySQL 5.7)
--help,
 -? 
:
Display help text and exit
:
(Supported in all NDB releases based on MySQL 5.7)
 --initial 
:
Perform initial start of ndbd, including file system cleanup; consult
 documentation before using this option
:
(Supported in all NDB releases based on MySQL 5.7)
 --initial-start 
:
Perform partial initial start (requires --nowait-nodes)
:
(Supported in all NDB releases based on MySQL 5.7)
 --install[=name] 
:
Used to install data node process as Windows service; does not apply on
 other platforms
:
(Supported in all NDB releases based on MySQL 5.7)
 --logbuffer-size=# 
:
Control size of log buffer; for use when debugging with many log
 messages being generated; default is sufficient for normal
 operations
:
ADDED: NDB 7.6.6
 --login-path=path 
:
Read given path from login file
:
(Supported in all NDB releases based on MySQL 5.7)
--ndb-connectstring=connection-string,
 -c 
:
Set connect string for connecting to ndb_mgmd. Syntax:
 "[nodeid=id;][host=]hostname[:port]". Overrides entries in
 NDB_CONNECTSTRING and my.cnf
:
(Supported in all NDB releases based on MySQL 5.7)
--ndb-mgmd-host=connection-string,
 -c 
:
Same as --ndb-connectstring
:
(Supported in all NDB releases based on MySQL 5.7)
 --ndb-nodeid=# 
:
Set node ID for this node, overriding any ID set by --ndb-connectstring
:
(Supported in all NDB releases based on MySQL 5.7)
 --nodaemon 
:
Do not start ndbd as daemon; provided for testing purposes
:
(Supported in all NDB releases based on MySQL 5.7)
 --no-defaults 
:
Do not read default options from any option file other than login file
:
(Supported in all NDB releases based on MySQL 5.7)
--nostart,
 -n 
:
Do not start ndbd immediately; ndbd waits for command to start from
 ndb_mgm
:
(Supported in all NDB releases based on MySQL 5.7)
 --nowait-nodes=list 
:
Do not wait for these data nodes to start (takes comma-separated list of
 node IDs); requires --ndb-nodeid
:
(Supported in all NDB releases based on MySQL 5.7)
 --ndb-optimized-node-selection 
:
Enable optimizations for selection of nodes for transactions. Enabled by
 default; use --skip-ndb-optimized-node-selection to
 disable
:
(Supported in all NDB releases based on MySQL 5.7)
 --print-defaults 
:
Print program argument list and exit
:
(Supported in all NDB releases based on MySQL 5.7)
 --remove[=name] 
:
Used to remove data node process that was previously installed as
 Windows service; does not apply on other platforms
:
(Supported in all NDB releases based on MySQL 5.7)
--usage,
 -? 
:
Display help text and exit; same as --help
:
(Supported in all NDB releases based on MySQL 5.7)
--verbose,
 -v 
:
Write extra debugging information to node log
:
(Supported in all NDB releases based on MySQL 5.7)
--version,
 -V 
:
Display version information and exit
:
(Supported in all NDB releases based on MySQL 5.7)

.\}


.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1


Note




All of these options also apply to the multithreaded version of this program (ndbmtd) and you may substitute
"ndbmtd"
for
"ndbd"
wherever the latter occurs in this section.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--bind-address






Command-Line Format
:
--bind-address=name
Type
:
String
Default Value
:

Causes
ndbd
to bind to a specific network interface (host name or IP address). This option has no default value.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--character-sets-dir




Command-Line Format
:
--character-sets-dir=path

Directory containing character sets.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--connect-delay=#









Command-Line Format
:
--connect-delay=#
Deprecated
:
Yes
Type
:
Numeric
Default Value
:
5
Minimum Value
:
0
Maximum Value
:
3600

Determines the time to wait between attempts to contact a management server when starting (the number of attempts is controlled by the
--connect-retries
option). The default is 5 seconds.
This option is deprecated, and is subject to removal in a future release of NDB Cluster. Use
--connect-retry-delay
instead.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--connect-retries=#








Command-Line Format
:
--connect-retries=#
Type
:
Numeric
Default Value
:
12
Minimum Value
:
0
Maximum Value
:
65535

Set the number of times to retry a connection before giving up; 0 means 1 attempt only (and no retries). The default is 12 attempts. The time to wait between attempts is controlled by the
--connect-retry-delay
option.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--connect-retry-delay=#








Command-Line Format
:
--connect-retry-delay=#
Type
:
Numeric
Default Value
:
5
Minimum Value
:
0
Maximum Value
:
4294967295

Determines the time to wait between attempts to contact a management server when starting (the time between attempts is controlled by the
--connect-retries
option). The default is 5 seconds.
This option takes the place of the
--connect-delay
option, which is now deprecated and subject to removal in a future release of NDB Cluster.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--connect-string






Command-Line Format
:
--connect-string=connection-string
Type
:
String
Default Value
:
[none]

Same as
--ndb-connectstring.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--core-file




Command-Line Format
:
--core-file

Write core file on error; used in debugging.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--daemon,
-d






Command-Line Format
:
--daemon
Type
:
Boolean
Default Value
:
TRUE

Instructs
ndbd
or
ndbmtd
to execute as a daemon process. This is the default behavior.
--nodaemon
can be used to prevent the process from running as a daemon.
This option has no effect when running
ndbd
or
ndbmtd
on Windows platforms.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--defaults-extra-file






Command-Line Format
:
--defaults-extra-file=path
Type
:
String
Default Value
:
[none]

Read given file after global files are read.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--defaults-file






Command-Line Format
:
--defaults-file=path
Type
:
String
Default Value
:
[none]

Read default options from given file only.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--defaults-group-suffix






Command-Line Format
:
--defaults-group-suffix=string
Type
:
String
Default Value
:
[none]

Also read groups with concat(group, suffix).




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--foreground






Command-Line Format
:
--foreground
Type
:
Boolean
Default Value
:
FALSE

Causes
ndbd
or
ndbmtd
to execute as a foreground process, primarily for debugging purposes. This option implies the
--nodaemon
option.
This option has no effect when running
ndbd
or
ndbmtd
on Windows platforms.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--help




Command-Line Format
:
--help

Display help text and exit.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--initial






Command-Line Format
:
--initial
Type
:
Boolean
Default Value
:
FALSE

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. On some operating systems, this process can take a substantial amount of time.
An
--initial
start is to be used
only
when starting the
ndbd
process under very special circumstances; this is because this option causes all files to be removed from the NDB Cluster file system and all redo log files to be re-created. These circumstances are listed here:


\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
When performing a software upgrade which has changed the contents of any files.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
When restarting the node with a new version of
ndbd.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
As a measure of last resort when for some reason the node restart or system restart repeatedly fails. In this case, be aware that this node can no longer be used to restore data due to the destruction of the data files.


.\}


.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1


Warning


To avoid the possibility of eventual data loss, it is recommended that you
not
use the
--initial
option together with
StopOnError = 0. Instead, set
StopOnError
to 0 in
config.ini
only after the cluster has been started, then restart the data nodes normally\(emthat is, without the
--initial
option. See the description of the
StopOnError
parameter for a detailed explanation of this issue. (Bug #24945638)


Use of this option prevents the
StartPartialTimeout
and
StartPartitionedTimeout
configuration parameters from having any effect.
.\}


.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1


Important


This option does
not
affect either of the following types of files:


\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
Backup files that have already been created by the affected node




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
NDB Cluster Disk Data files (see
Section 21.5.10, "NDB Cluster Disk Data Tables").


This option also has no effect on recovery of data by a data node that is just starting (or restarting) from data nodes that are already running. This recovery of data occurs automatically, and requires no user intervention in an NDB Cluster that is running normally.


It is permissible to use this option when starting the cluster for the very first time (that is, before any data node files have been created); however, it is
not
necessary to do so.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--initial-start






Command-Line Format
:
--initial-start
Type
:
Boolean
Default Value
:
FALSE

This option is used when performing a partial initial start of the cluster. Each node should be started with this option, as well as
--nowait-nodes.
Suppose that 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\(emthat is, omitting node 3:


.\}

shell> ndbd --ndb-nodeid=2 --nowait-nodes=3 --initial-start
shell> ndbd --ndb-nodeid=4 --nowait-nodes=3 --initial-start
shell> ndbd --ndb-nodeid=5 --nowait-nodes=3 --initial-start




.\}
When using this option, you must also specify the node ID for the data node being started with the
--ndb-nodeid
option.
.\}


.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1


Important


Do not confuse this option with the
--nowait-nodes
option for
ndb_mgmd, which can be used to enable a cluster configured with multiple management servers to be started without all management servers being online.






\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--install[=name]







Command-Line Format
:
--install[=name]
Platform Specific
:
Windows
Type
:
String
Default Value
:
ndbd

Causes
ndbd
to be installed as a Windows service. Optionally, you can specify a name for the service; if not set, the service name defaults to
ndbd. Although it is preferable to specify other
ndbd
program options in a
my.ini
or
my.cnf
configuration file, it is possible to use together with
--install. However, in such cases, the
--install
option must be specified first, before any other options are given, for the Windows service installation to succeed.
It is generally not advisable to use this option together with the
--initial
option, since this causes the data node file system to be wiped and rebuilt every time the service is stopped and started. Extreme care should also be taken if you intend to use any of the other
ndbd
options that affect the starting of data nodes\(emincluding
--initial-start,
--nostart, and
--nowait-nodes\(emtogether with
--install, and you should make absolutely certain you fully understand and allow for any possible consequences of doing so.
The
--install
option has no effect on non-Windows platforms.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--logbuffer-size=#









Command-Line Format
:
--logbuffer-size=#
Introduced
:
5.7.22-ndb-7.6.6
Type
:
Integer
Default Value
:
32768
Minimum Value
:
2048
Maximum Value
:
4294967295

Sets the size of the data node log buffer. When debugging with high amounts of extra logging, it is possible for the log buffer to run out of space if there are too many log messages, in which case some log messages can be lost. This should not occur during normal operations.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--login-path






Command-Line Format
:
--login-path=path
Type
:
String
Default Value
:
[none]

Read given path from login file.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--ndb-connectstring






Command-Line Format
:
--ndb-connectstring=connection-string
Type
:
String
Default Value
:
[none]

Set connect string for connecting to ndb_mgmd. Syntax: "[nodeid=id;][host=]hostname[:port]". Overrides entries in NDB_CONNECTSTRING and my.cnf.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--ndb-mgmd-host






Command-Line Format
:
--ndb-mgmd-host=connection-string
Type
:
String
Default Value
:
[none]

Same as
--ndb-connectstring.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--ndb-nodeid






Command-Line Format
:
--ndb-nodeid=#
Type
:
Integer
Default Value
:
[none]

Set node ID for this node, overriding any ID set by
--ndb-connectstring.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--ndb-optimized-node-selection




Command-Line Format
:
--ndb-optimized-node-selection

Enable optimizations for selection of nodes for transactions. Enabled by default; use
--skip-ndb-optimized-node-selection
to disable.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--nodaemon






Command-Line Format
:
--nodaemon
Type
:
Boolean
Default Value
:
FALSE

Prevents
ndbd
or
ndbmtd
from executing as a daemon process. This option overrides the
--daemon
option. This is useful for redirecting output to the screen when debugging the binary.
The default behavior for
ndbd
and
ndbmtd
on Windows is to run in the foreground, making this option unnecessary on Windows platforms, where it has no effect.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--no-defaults




Command-Line Format
:
--no-defaults

Do not read default options from any option file other than login file.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--nostart,
-n






Command-Line Format
:
--nostart
Type
:
Boolean
Default Value
:
FALSE

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 21.5.1, "Commands in the NDB Cluster Management Client").




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--nowait-nodes=node_id_1[, node_id_2[, ...]]






Command-Line Format
:
--nowait-nodes=list
Type
:
String
Default Value
:

This option takes a list of data nodes which for which the cluster does 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
--nowait-nodes=3. Then the cluster starts as soon as nodes 2, 4, and 5 connect and does not wait for node 3 to start.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--print-defaults




Command-Line Format
:
--print-defaults

Print program argument list and exit.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--remove[=name]







Command-Line Format
:
--remove[=name]
Platform Specific
:
Windows
Type
:
String
Default Value
:
ndbd

Causes an
ndbd
process that was previously installed as a Windows service to be removed. Optionally, you can specify a name for the service to be uninstalled; if not set, the service name defaults to
ndbd.
The
--remove
option has no effect on non-Windows platforms.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--usage




Command-Line Format
:
--usage

Display help text and exit; same as
--help.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--verbose,
-v
Causes extra debug output to be written to the node log.
In NDB 7.6.4 and later, you can also use
NODELOG DEBUG ON
and
NODELOG DEBUG OFF
to enable and disable this extra logging while the data node is running.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
--version




Command-Line Format
:
--version

Display version information and exit.




ndbd
generates a set of log files which are placed in the directory specified by
DataDir
in the
config.ini
configuration file.


These log files are listed below.
node_id
is and represents the node\*(Aqs unique identifier. For example,
ndb_2_error.log
is the error log generated by the data node whose node ID is
2.


\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
ndb_node_id_error.log
is a file containing records of all crashes which the referenced
ndbd
process has encountered. Each record in this file contains a brief error string and a reference to a trace file for this crash. A typical entry in this file might appear as shown here:


.\}

Date/Time: Saturday 30 July 2004 - 00:20:01
Type of error: error
Message: Internal program error (failed ndbrequire)
Fault ID: 2341
Problem data: DbtupFixAlloc.cpp
Object of reference: DBTUP (Line: 173)
ProgramName: NDB Kernel
ProcessID: 14909
TraceFile: ndb_2_trace.log.2
***EOM***




.\}
Listings of possible
ndbd
exit codes and messages generated when a data node process shuts down prematurely can be found in
\m[blue]Data Node Error Messages\m[]\s-2\u[1]\d\s+2.
.\}


.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1


Important


The last entry in the error log file is not necessarily the newest one
(nor is it likely to be). Entries in the error log are
not
listed in chronological order; rather, they correspond to the order of the trace files as determined in the
ndb_node_id_trace.log.next
file (see below). Error log entries are thus overwritten in a cyclical and not sequential fashion.






\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
ndb_node_id_trace.log.trace_id
is a trace file describing exactly what happened just before the error occurred. This information is useful for analysis by the NDB Cluster development team.
It is possible to configure the number of these trace files that are created before old files are overwritten.
trace_id
is a number which is incremented for each successive trace file.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
ndb_node_id_trace.log.next
is the file that keeps track of the next trace file number to be assigned.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
ndb_node_id_out.log
is a file containing any data output by the
ndbd
process. This file is created only if
ndbd
is started as a daemon, which is the default behavior.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
ndb_node_id.pid
is a file containing the process ID of the
ndbd
process when started as a daemon. It also functions as a lock file to avoid the starting of nodes with the same identifier.




\h'-04'\(bu\h'+03'\c
.\}

 \(bu 2.3
.\}
ndb_node_id_signal.log
is a file used only in debug versions of
ndbd, where it is possible to trace all incoming, outgoing, and internal messages with their data in the
ndbd
process.




It is recommended not to use a directory mounted through NFS because in some environments this can cause problems whereby the lock on the
.pid
file remains in effect even after the process has terminated.


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 21.3.3.3, "NDB Cluster Connection Strings", for additional information about this issue. For more information about data node configuration parameters, see
Section 21.3.3.6, "Defining NDB Cluster Data Nodes".


When
ndbd
starts, it actually initiates two processes. The first of these is called the
"angel process"; its only job is to discover when the execution process has been completed, and then to restart the
ndbd
process if it is configured to do so. Thus, if you attempt to kill
ndbd
using the Unix
kill
command, it is necessary to kill both processes, beginning with the angel process. The preferred method of terminating an
ndbd
process is to use the management client and stop the process from there.


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
ndbd
process. In a multi-processor system performing a large number of operations (including updates), the
ndbd
process can consume up to 2 CPUs if permitted to do so.


For a machine with many CPUs it is possible to use several
ndbd
processes which belong to different node groups; however, such a configuration is still considered experimental and is not supported for MySQL 5.7 in a production setting. See
Section 21.1.7, "Known Limitations of NDB Cluster".

 "COPYRIGHT"



Copyright \(co 1997, 2021, Oracle and/or its affiliates.


This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.


This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.


You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/.

 "NOTES"
 " 1." 4
Data Node Error Messages


\%https://dev.mysql.com/doc/ndb-internals/en/ndb-node-error-messages.html



 "SEE ALSO"
For more information, please refer to the MySQL Reference Manual,
which may already be installed locally and which is also available
online at http://dev.mysql.com/doc/.

 AUTHOR
Oracle Corporation (http://dev.mysql.com/).