Users of earlier MySQL Cluster versions should note that some
of these options have been changed to make them consistent
with one another, and also with mysqld. You
can use the --help option with any MySQL
Cluster program—with the exception of
ndb_print_backup_file,
ndb_print_schema_file, and
ndb_print_sys_file—to view a list of
the options which the program supports.

The options in the following table are common to all MySQL
Cluster executables (except those noted previously in this
section).

Table 18.98
This table describes command-line options
common to all MySQL Cluster programs

Write a core file if the program dies. The name and location
of the core file are system-dependent. (For MySQL Cluster
programs nodes running on Linux, the default location is the
program's working directory—for a data node, this
is the node's
DataDir.) For some
systems, there may be restrictions or limitations; for
example, it might be necessary to execute ulimit -c
unlimited before starting the server. Consult your
system documentation for detailed information.

If MySQL Cluster was built using the
--debug option for
configure, then
--core-file is enabled by default. For
regular builds, --core-file is disabled by
default.

--debug[=options]

Command-Line Format

--debug=options

Permitted Values

Type

string

Default

d:t:O,/tmp/ndb_restore.trace

This option can be used only for versions compiled with
debugging enabled. It is used to enable output from debug
calls in the same manner as for the
mysqld process.

--ndb-mgmd-host=host[:port]

Command-Line Format

--ndb-mgmd-host=host[:port]

Permitted Values

Type

string

Default

localhost:1186

Can be used to set the host and port number of a single
management server for the program to connect to. If the
program requires node IDs or references to multiple
management servers (or both) in its connection information,
use the
--ndb-connectstring
option instead.

Prints the MySQL Cluster version number of the executable.
The version number is relevant because not all versions can
be used together, and the MySQL Cluster startup process
verifies that the versions of the binaries being used can
co-exist in the same cluster. This is also important when
performing an online (rolling) software upgrade or downgrade
of MySQL Cluster.