content_image/850194.jpg content_image/850195.jpg content_image/850196.jpg content_image/850197.jpg
performing a rolling restart of an NDB Cluster with multiple management nodes. See Section 23.5.5, “Performing a Rolling Restart of an NDB Cluster” , for more information. 

When used together with the --config-file  option, the cache is cleared only if the configuration file is actually found. 

• --install[= name ] 

<img src='content_image/850194.jpg'>

Causes ndb_mgmd  to be installed as a Windows service. Optionally, you can specify a name for the service; if not set, the service name defaults to ndb_mgmd . Although it is preferable to specify other ndb_mgmd  program options in a my.ini  or my.cnf  configuration file, it is possible to use them together with --install . However, in such cases, the --install  option must be specified first, before any other options are given, for the Windows service installation to succeed. 

It is generally not advisable to use this option together with the --initial  option, since this causes the configuration cache to be wiped and rebuilt every time the service is stopped and started. Care should also be taken if you intend to use any other ndb_mgmd  options that affect the starting of the management server, and you should make absolutely certain you fully understand and allow for any possible consequences of doing so. 

The --install  option has no effect on non-Windows platforms. 

• --interactive 

<img src='content_image/850195.jpg'>

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 NDB Cluster nodes. 

• --log-name= name 

<img src='content_image/850196.jpg'>

Provides a name to be used for this node in the cluster log. 

• --login-path 

<img src='content_image/850197.jpg'>

Read given path from login file. 

