NDB_MGMD(8)

NAME
ndb_mgmd - the MySQL Cluster management server daemon

SYNOPSIS

ndb_mgmd options

DESCRIPTION

The management server is the process that reads the cluster configuration file and distributes this information to all nodes in the cluster that request it. It also maintains a log of cluster activities. Management clients can connect to the management server and check the cluster's status.

The following table includes command options specific to the MySQL Cluster management node program ndb_mgmd. Additional descriptions follow the table. For options common to all MySQL Cluster programs, see Section 16.4.2, “Options Common to MySQL Cluster Programs”.

    • --no-nodeid-checks
    Command-Line Format | --no-nodeid-checks
     | Permitted Values
     | Type | boolean
     | Default | FALSE

    Do not perform any checks of node IDs.

    • --config-file=filename, -f filename
    Command-Line Format | --config-file
     | -f
     | -c
     | Permitted Values
     | Type | file name
     | Default | ./config.ini

    Instructs the management server as to which file it should use for its configuration file. By default, the management server looks for a file named config.ini in the same directory as the ndb_mgmd executable; otherwise the file name and location must be specified explicitly.

    This option also can be given as -c file_name, but this shortcut is obsolete and should not be used in new installations.

    • --mycnf
    Command-Line Format | --mycnf
     | Permitted Values
     | Type | boolean
     | Default | FALSE

    Read configuration data from the my.cnf file.

    • --daemon, -d
    Command-Line Format | --daemon
     | -d
     | Permitted Values
     | Type | boolean
     | Default | TRUE

    Instructs ndb_mgmd to start as a daemon process. This is the default behavior.

    • --interactive
    Command-Line Format | --interactive
     | Permitted Values
     | Type | boolean
     | Default | FALSE

    Starts ndb_mgmd in interactive mode; that is, an ndb_mgm client session is started as soon as the management server is running. This option does not start any other MySQL Cluster nodes.

    • --nodaemon
    Command-Line Format | --nodaemon
     | Permitted Values
     | Type | boolean
     | Default | FALSE
     | Permitted Values
     | Type (windows) | boolean
     | Default | TRUE

    Instructs ndb_mgmd not to start as a daemon process.

    • --print-full-config, -P
    Version Introduced | 5.0.10
    Command-Line Format | --print-full-config
     | -P
     | Permitted Values
     | Type | boolean
     | Default | FALSE

    Shows extended information regarding the configuration of the cluster. With this option on the command line the ndb_mgmd process prints information about the cluster setup including an extensive list of the cluster configuration sections as well as parameters and their values. Normally used together with the --config-file (-f) option.

It is not strictly necessary to specify a connectstring when starting the management server. However, if you are using more than one management server, a connectstring should be provided and each node in the cluster should specify its node ID explicitly.

See Section 16.3.2.2, “The MySQL Cluster Connectstring”, for information about using connectstrings. ndb_mgmd(8), describes other options for ndb_mgmd.

The following files are created or used by ndb_mgmd in its starting directory, and are placed in the DataDir as specified in the config.ini configuration file. In the list that follows, node_id is the unique node identifier.

    • config.ini is the configuration file for the cluster as a whole. This file is created by the user and read by the management server. Section 16.3, “MySQL Cluster Configuration”, discusses how to set up this file.

    • ndb_node_id_cluster.log is the cluster events log file. Examples of such events include checkpoint startup and completion, node startup events, node failures, and levels of memory usage. A complete listing of cluster events with descriptions may be found in Section 16.5, “Management of MySQL Cluster”.

    When the size of the cluster log reaches one million bytes, the file is renamed to ndb_node_id_cluster.log.seq_id, where seq_id is the sequence number of the cluster log file. (For example: If files with the sequence numbers 1, 2, and 3 already exist, the next log file is named using the number 4.)

    • ndb_node_id_out.log is the file used for stdout and stderr when running the management server as a daemon.

    • ndb_node_id.pid is the process ID file used when running the management server as a daemon.

COPYRIGHT

Copyright © 1997, 2011, Oracle and/or its affiliates. All rights reserved.

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/.

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/).