All MySQL Cluster programs (except for
mysqld) take the options described in this
section as of MySQL 4.1.8. Users of earlier MySQL Cluster
versions should note that some of these options have been
changed to make consistent with one another as well as with
mysqld. You can use the
--help option with any MySQL Cluster program to
view a list of the options which it supports.
Table 15.16 Common MySQL Cluster Command line Options
|--character-sets-dir=path||Directory where character sets are installed|
|--core-file||Write core on errors (defaults to TRUE in debug builds)|
|--debug=options||Enable output from debug calls. Can be used only for versions compiled with debugging enabled|
|--help, --usage||Display help message and exit|
|--connect-string=connectstring, --ndb-connectstring=connectstring||Set connection string for connecting to ndb_mgmd. Syntax: [nodeid=<id>;][host=]<hostname>[:<port>]. Overrides entries specified in NDB_CONNECTSTRING or my.cnf.|
|--ndb-mgmd-host=host[:port]||Set the host (and port, if desired) for connecting to management server|
|--ndb-nodeid=#||Set node id for this node|
|--ndb-optimized-node-selection||Select nodes for transactions in a more optimal way|
|--ndb-shm||Allow for optimization using shared memory connections where available (was EXPERIMENTAL, later REMOVED)|
|--version||Output version information and exit|
For options specific to individual MySQL Cluster programs, see Section 15.4, “MySQL Cluster Programs”.
See Section 126.96.36.199, “mysqld Command Options for MySQL Cluster”, for mysqld options relating to MySQL Cluster.
Prints a short list with descriptions of the available command options.
Tells the program where to find character set information.
connect_string sets the
connectstring to the management server as a command option.
Available with ndb_mgm beginning with
For more information, see Section 188.8.131.52, “The MySQL Cluster Connectstring”.
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
--core-file is enabled by default. For
--core-file is disabled by
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.
Can be used to set the host and port number of the management server to connect to.
Sets this node's MySQL Cluster node ID. The range of permitted values depends on the type of the node (data, management, or API) and the version of the MySQL Cluster software which is running on it. See Section 184.108.40.206, “Limits and Differences of MySQL Cluster from Standard MySQL Limits”, for more information.
Optimize selection of nodes for transactions. Enabled by default.
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. (See Section 220.127.116.11, “Performing a Rolling Restart of a MySQL Cluster”).