- 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 following table provides information about parameters used
in the [SQL] and [api]
sections of a config.ini file for
configuring MySQL Cluster SQL nodes and API nodes. For detailed
descriptions and other additional information about each of
these parameters, see
Section 17.3.2.6, “Defining SQL and Other API Nodes in a MySQL Cluster”.
Note
For a discussion of MySQL server options for MySQL Cluster, see Section 17.3.4.2, “mysqld Command Options for MySQL Cluster”; for information about MySQL server system variables relating to MySQL Cluster, see Section 17.3.4.3, “MySQL Cluster System Variables”.
Table 17.3. API Node Configuration Parameters
| Name | Type/Units | Default | Min Value | Max Value | Restart Type |
|---|---|---|---|---|---|
| ArbitrationDelay | milliseconds | 4G | N | ||
| ArbitrationRank | 0-2 | 2 | N | ||
| BatchByteSize | bytes | 32K | 1024 | 1M | N |
| ExecuteOnComputer | name | S | |||
| HostName | name or IP | S | |||
| Id | unsigned | 1 | 63 | N | |
| MaxScanBatchSize | bytes | 256K | 32K | 16M | N |
Note
To add new SQL or API nodes to the configuration of a running
MySQL 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.
User Comments
Add your own comment.