|
 |
|
| |
16.5.5.2. Command Options for ndbd
For options common to NDB programs, see
Section 16.5.5, “Command Options for MySQL Cluster Processes”.
-
--daemon, -d
Instructs ndbd to execute as a daemon
process. This is the default behavior.
--nodaemon can be used to not start the
process 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:
When performing a software upgrade which has changed
the contents of any files.
When restarting the node with a new version of
ndbd.
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
datafiles.
This option does not affect any backup files that have
already been created by the affected node.
-
--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
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 command to the management client.
|
|
|
