The following table provides information about parameters used
in the [ndb_mgmd]
or [mgm]
sections of a config.ini
file for
configuring MySQL Cluster management nodes. For detailed
descriptions and other additional information about each of
these parameters, see
Section 3.2.5, “Defining a MySQL Cluster Management Server”.
Table 3.2. Management Node Configuration Parameters
Name | Type/Units | Default | Min Value | Max Value | Restart Type |
---|---|---|---|---|---|
ArbitrationDelay | milliseconds | 4G | N | ||
ArbitrationRank | 0-2 | 1 | 2 | N | |
DataDir | path | . | N | ||
ExecuteOnComputer | name | S | |||
HostName | name or IP | S | |||
Id | unsigned | 1 | 63 | N | |
LogDestination | {CONSOLE|SYSLOG|FILE} | FILE:filename=ndb_nodeid_cluster.log,maxsize=1000000,maxfiles=6 | N | ||
MaxNoOfSavedEvents | unsigned | 100 | 4G | N | |
PortNumber | unsigned | 1186 | 64K | N | |
PortNumberStats | unsigned | 64K | N | ||
wan | false | N |
After making changes in a management node's configuration, it is necessary to perform a rolling restart of the cluster in order for the new configuration to take effect. See Section 3.2.5, “Defining a MySQL Cluster Management Server”, for more information.
To add new management servers to a running MySQL Cluster, it
is also necessary perform a rolling restart of all cluster
nodes after modifying any existing
config.ini
files. For more information
about issues arising when using multiple management nodes, see
Section 1.5.10, “Limitations Relating to Multiple MySQL Cluster Nodes”.