17.3.3.3. MySQL Cluster SQL Node and API Node Configuration Parameters

The summary table in this section provides information about parameters used in the [mysqld] 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.7, "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, "MySQL Server 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".

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 --initial option.

For more information about restart types, see Section 17.3.3, "Overview of MySQL Cluster Configuration Parameters".

Table 17.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
`ArbitrationDelay`	milliseconds	N	NDB 7.3.0
	0
	0 / 4G
`ArbitrationRank`	0-2	N	NDB 7.3.0
	0
	0 / 2
`AutoReconnect`	boolean	N	NDB 7.3.0
	false
	true, false
`BatchByteSize`	bytes	N	NDB 7.3.0
	16K
	1024 / 1M
`BatchSize`	records	N	NDB 7.3.0
	256
	1 / 992
`ConnectionMap`	string	N	NDB 7.3.0
	[none]
	...
`DefaultHashMapSize`	LDM threads	N	NDB 7.3.0
	3840
	0 / 3840
`DefaultOperationRedoProblemAction`	enumeration	S	NDB 7.3.0
	QUEUE
	ABORT, QUEUE
`ExecuteOnComputer`	name	S	NDB 7.3.0
	[none]
	...
`HeartbeatThreadPriority`	string	S	NDB 7.3.0
	[none]
	...
`HostName`	name or IP address	S	NDB 7.3.0
	[none]
	...
`Id`	unsigned	IS	NDB 7.3.0
	[none]
	1 / 255
`MaxScanBatchSize`	bytes	N	NDB 7.3.0
	256K
	32K / 16M
`NodeId`	unsigned	IS	NDB 7.3.0
	[none]
	1 / 255
`TotalSendBufferMemory`	bytes	N	NDB 7.3.0
	256K
	0 / 4G
`wan`	boolean	N	NDB 7.3.0
	false
	true, false

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.