- Documentation Library
- Table of Contents
- MySQL 5.7 Manual
- MySQL 5.6 Manual
- MySQL 5.5 Manual
- MySQL 5.1 Manual
- MySQL 5.0 Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
- 15.4 MySQL Cluster Programs
- 15.4.1 MySQL Server Usage for MySQL Cluster
- 15.4.2 ndbd — The MySQL Cluster Data Node Daemon
- 15.4.3 ndb_mgmd — The MySQL Cluster Management Server Daemon
- 15.4.4 ndb_mgm — The MySQL Cluster Management Client
- 15.4.5 ndb_config — Extract MySQL Cluster Configuration Information
- 15.4.6 ndb_cpcd — Automate Testing for NDB Development
- 15.4.7 ndb_delete_all — Delete All Rows from an NDB Table
- 15.4.8 ndb_desc — Describe NDB Tables
- 15.4.9 ndb_drop_index — Drop Index from an NDB Table
- 15.4.10 ndb_drop_table — Drop an NDB Table
- 15.4.11 ndb_error_reporter — NDB Error-Reporting Utility
- 15.4.12 ndb_print_backup_file — Print NDB Backup File Contents
- 15.4.13 ndb_print_schema_file — Print NDB Schema File Contents
- 15.4.14 ndb_print_sys_file — Print NDB System File Contents
- 15.4.15 ndb_restore — Restore a MySQL Cluster Backup
- 15.4.16 ndb_select_all — Print Rows from an NDB Table
- 15.4.17 ndb_select_count — Print Row Counts for NDB Tables
- 15.4.18 ndb_show_tables — Display List of NDB Tables
- 15.4.19 ndb_size.pl — NDBCLUSTER Size Requirement Estimator
- 15.4.20 ndb_waiter — Wait for MySQL Cluster to Reach a Given Status
- 15.4.21 Options Common to MySQL Cluster Programs
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
| Format | Description |
|---|---|
| --character-sets-dir=path | Directory where character sets are |
| --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 | Display help message and exit |
| --ndb-connectstring=connectstring | Set connectstring 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 the 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 15.3.4.2, “mysqld Command Options for MySQL Cluster”, for mysqld options relating to MySQL Cluster.
-
Command-Line Format --help--usage-?Prints a short list with descriptions of the available command options.
-
Command-Line Format --character-sets-dir=pathPermitted Values Type file nameDefault Tells the program where to find character set information.
--connect-string=connect_stringCommand-Line Format --ndb-connectstring=connectstring--connect-string=connectstring-cPermitted Values Type stringDefault localhost:1186connect_stringsets the connectstring to the management server as a command option. Available with ndb_mgm beginning with MySQL 4.1.8.shell>
ndbd --connect-string="nodeid=2;host=ndb_mgmd.mysql.com:1186"-
Command-Line Format --core-filePermitted Values Type booleanDefault FALSEWrite 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
--debugoption for configure, then--core-fileis enabled by default. For regular builds,--core-fileis disabled by default. -
Command-Line Format --debug=optionsPermitted Values Type stringDefault d:t:O,/tmp/ndb_restore.traceThis 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.
-
Command-Line Format --ndb-mgmd-host=host[:port]Option-File Format ndb-mgmd-hostPermitted Values Type stringDefault localhost:1186Can be used to set the host and port number of the management server to connect to.
-
Command-Line Format --ndb-nodeid=#Permitted Values Type numericDefault 0Sets 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 15.1.4.2, “Limits and Differences of MySQL Cluster from Standard MySQL Limits”, for more information.
--ndb-optimized-node-selectionCommand-Line Format --ndb-optimized-node-selectionPermitted Values Type booleanDefault TRUEOptimize selection of nodes for transactions. Enabled by default.
-
Command-Line Format --version-VPrints 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 15.2.6.1, “Performing a Rolling Restart of a MySQL Cluster”).
User Comments
Add your own comment.