The summary table in this section provides information about
parameters used in the [mysqld] and
[api] sections of a
config.ini file for configuring NDB Cluster
SQL nodes and API nodes. For detailed descriptions and other
additional information about each of these parameters, see
Section 18.3.3.7, “Defining SQL and Other API Nodes in an NDB Cluster”.
For a discussion of MySQL server options for NDB Cluster, see Section 18.3.3.8.1, “MySQL Server Options for NDB Cluster”; for information about MySQL server system variables relating to NDB Cluster, see Section 18.3.3.8.2, “NDB Cluster System Variables”.
Restart types. Changes in NDB 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 18.5.5, “Performing a Rolling Restart of an NDB 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
--initial option.
For more information about restart types, see Section 18.3.2, “Overview of NDB Cluster Configuration Parameters, Options, and Variables”.
Table 18.4 SQL Node / API Node Configuration Parameters
| Parameter Name | Type or Units | Restart Type | In Version ... (and later) |
|---|---|---|---|
| Default Value | |||
| Minimum/Maximum or Permitted Values | |||
| bytes | N | NDB 7.4.12 | |
| undefined | |||
| 0 / 100 | |||
| milliseconds | N | NDB 7.3.0 | |
| 0 | |||
| 0 / 4294967039 (0xFFFFFEFF) | |||
| 0-2 | N | NDB 7.3.0 | |
| 0 | |||
| 0 / 2 | |||
| boolean | N | NDB 7.3.0 | |
| false | |||
| true, false | |||
| bytes | N | NDB 7.3.0 | |
| 16K | |||
| 1024 / 1M | |||
| records | N | NDB 7.3.0 | |
| 256 | |||
| 1 / 992 | |||
| integer | N | NDB 7.4.2 | |
| 0 | |||
| 0 / 4294967039 (0xFFFFFEFF) | |||
| string | N | NDB 7.3.0 | |
| [none] | |||
| ... | |||
| buckets | N | NDB 7.3.0 | |
| 3840 | |||
| 0 / 3840 | |||
| enumeration | S | NDB 7.3.0 | |
| QUEUE | |||
| ABORT, QUEUE | |||
| bytes | S | NDB 7.3.0 | |
| 8192 | |||
| 0 / 64K | |||
| name | S | NDB 7.3.0 | |
| [none] | |||
| ... | |||
| bytes | N | NDB 7.3.0 | |
| 0 | |||
| 0 / 4294967039 (0xFFFFFEFF) | |||
| string | S | NDB 7.3.0 | |
| [none] | |||
| ... | |||
| name or IP address | N | NDB 7.3.0 | |
| [none] | |||
| ... | |||
| unsigned | IS | NDB 7.3.0 | |
| [none] | |||
| 1 / 255 | |||
| bytes | N | NDB 7.3.0 | |
| 256K | |||
| 32K / 16M | |||
| unsigned | IS | NDB 7.3.0 | |
| [none] | |||
| 1 / 255 | |||
| integer | N | NDB 7.4.2 | |
| 0 | |||
| 0 / 4294967039 (0xFFFFFEFF) | |||
| bytes | N | NDB 7.3.0 | |
| 0 | |||
| 256K / 4294967039 (0xFFFFFEFF) | |||
| boolean | N | NDB 7.3.0 | |
| false | |||
| true, false |
To add new SQL or API nodes to the configuration of a running
NDB Cluster, it is necessary to perform a rolling restart of
all cluster nodes after adding new [mysqld]
or [api] sections to the
config.ini file (or files, if you are
using more than one management server). This must be done
before the new SQL or API nodes can connect to the cluster.
It is not necessary to perform any restart of the cluster if new SQL or API nodes can employ previously unused API slots in the cluster configuration to connect to the cluster.