DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 

(mysql.info.gz) ndb_mgmd process

Info Catalog (mysql.info.gz) ndbd process (mysql.info.gz) MySQL Cluster Process Management (mysql.info.gz) ndb_mgm process
 
 16.4.3 `ndb_mgmd', the Management Server Process
 ------------------------------------------------
 
 The management server is the process that reads the configuration file
 of the cluster and distributes this information to all nodes in the
 cluster requesting it. It also maintains the log of cluster activities.
 Management clients can connect to the management server and use
 commands to check status of the cluster in various aspects.
 
 As of MySQL 4.1.5, it is no longer necessary to specify a connectstring
 when starting the management server. However, if you are using several
 management servers, a connectstring should be provided and each node in
 the cluster should specify its nodeid explicitly.
 
 The following files are created or used by `ndb_mgmd' in its starting
 directory of `ndb_mgmd'. From MySQL 4.1.5, the log and PID files will
 be placed in the `DataDir' specified in the configuration file:
 
    * `config.ini' is the configuration file of the cluster. This is
      created by the user and read by the management server. How to
      write this file is described in the section `MySQL Cluster
      Configuration'.
 
    * `ndb_1_cluster.log' (was `cluster.log' in version 4.1.3) is the
      file where events in the cluster are reported.  Examples of events
      are checkpoints started and completed, node failures and nodes
      starting, levels of memory usage passed and so forth. The events
      reported are described in the section  MySQL Cluster
      Management.
 
    * `ndb_1_out.log' (was `node1.out' in version 4.1.3) is the file used
      for stdout and stderr when executing the management server as a
      daemon process. 1 in this context is the node ID.
 
    * `ndb_1.pid' (was `node1.pid' in version 4.1.3) is the PID file used
      when executing the management server as a daemon process. 1 in
      this context is the node ID.
 
    * `ndb_1_cluster.log.1' (was `cluster.log.1' in version 4.1.3) when
      the cluster log becomes bigger than one million bytes then the
      file is renamed to this name where 1 is the number of the cluster
      log file, so if 1, 2, and 3 exist the next will be having the
      number 4 instead.
 
Info Catalog (mysql.info.gz) ndbd process (mysql.info.gz) MySQL Cluster Process Management (mysql.info.gz) ndb_mgm process
automatically generated byinfo2html