- 17.3.3 Overview of MySQL Cluster Configuration Parameters
- 17.3.3.1 MySQL Cluster Data Node Configuration Parameters
- 17.3.3.2 MySQL Cluster Management Node Configuration Parameters
- 17.3.3.3 MySQL Cluster SQL Node and API Node Configuration Parameters
- 17.3.3.4 Other MySQL Cluster Configuration Parameters
The summary table in this section 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 17.3.2.5, “Defining a MySQL Cluster Management Server”.
Restart types. Changes in MySQL Cluster configuration parameters do not take effect until the cluster is restarted. The type of restart required to change a given parameter is indicated in the summary table as follows:
N—Node restart: The parameter can be updated using a rolling restart (see Section 17.5.5, “Performing a Rolling Restart of a MySQL Cluster”).S—System restart: The cluster must be shut down completely, then restarted, to effect a change in this parameter.I—Initial restart: Data nodes must be restarted using the--initialoption.
For more information about restart types, see Section 17.3.3, “Overview of MySQL Cluster Configuration Parameters”.
Table 17.3. Management Node Configuration Parameters
| Parameter Name | Type or Units | Restart Type | In Version ... (and later) |
|---|---|---|---|
| Default Value | |||
| Minimum/Maximum or Permitted Values | |||
| milliseconds | N | NDB 7.2.0 | |
| 0 | |||
| 0 / 4G | |||
| 0-2 | N | NDB 7.2.0 | |
| 1 | |||
| 0 / 2 | |||
| path | N | NDB 7.2.0 | |
| . | |||
| ... | |||
| name | S | NDB 7.2.0 | |
| [none] | |||
| ... | |||
| string | S | NDB 7.2.0 | |
| [none] | |||
| ... | |||
| name or IP address | S | NDB 7.2.0 | |
| [none] | |||
| ... | |||
| unsigned | IS | NDB 7.2.0 | |
| [none] | |||
| 1 / 255 | |||
| {CONSOLE|SYSLOG|FILE} | N | NDB 7.2.0 | |
| [see text] | |||
| ... | |||
| unsigned | N | NDB 7.2.0 |
| 100 | |||
| 0 / 4G | |||
| unsigned | IS | NDB 7.2.0 | |
| [none] | |||
| 1 / 255 | |||
| unsigned | N | NDB 7.2.0 | |
| 1186 | |||
| 0 / 64K | |||
| unsigned | N | NDB 7.2.0 |
| [none] | |||
| 0 / 64K | |||
| bytes | N | NDB 7.2.0 | |
| 256K | |||
| 0 / 4G | |||
| boolean | N | NDB 7.2.0 |
| false | |||
| true, false |
After making changes in a management node's configuration, it is necessary to perform a rolling restart of the cluster for the new configuration to take effect. See Section 17.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 17.1.6.10, “Limitations Relating to Multiple MySQL Cluster Nodes”.
User Comments
Add your own comment.