Oracle 5.0 Reference Manual page 1614

parameters marked as
initial node restart requires restarting each
A system restart requires a complete shutdown and restart of the entire cluster. An initial system restart
requires taking a backup of the cluster, wiping the cluster file system after shutdown, and then restoring
from the backup following the restart.
In any cluster restart, all of the cluster's management servers must be restarted for them to read the
updated configuration parameter values.
Because some of these parameters can be used for configuring more than one type of cluster node,
they may appear in more than one of the tables.
17.3.3.1. MySQL Cluster Data Node Configuration Parameters
The summary table in this section provides information about parameters used in the
or
[ndbd default]
For detailed descriptions and other additional information about each of these parameters, see
Section 17.3.2.5, "Defining MySQL Cluster Data
Restart types.
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
"Performing a Rolling Restart of a MySQL
• 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
For more information about restart types, see
Configuration
Overview of MySQL Cluster Configuration Parameters
online—that is, without shutting down the cluster—in this fashion. An
node
Important
Values for numeric cluster parameters can generally be increased without
any problems, although it is advisable to do so progressively, making such
adjustments in relatively small increments. Many of these can be increased
online, using a rolling restart.
However, decreasing the values of such parameters—whether this is
done using a node restart, node initial restart, or even a complete system
restart of the cluster—is not to be undertaken lightly; it is recommended
that you do so only after careful planning and testing. This is especially
true with regard to those parameters that relate to memory usage and
disk space, such as MaxNoOfTables, MaxNoOfOrderedIndexes, and
MaxNoOfUniqueHashIndexes. In addition, it is the generally the case that
configuration parameters relating to memory and disk usage can be raised
using a simple node restart, but they require an initial node restart to be
lowered.
Note
4294967039—which often appears as a maximum value in these tables—
is defined in the
NDBCLUSTER
0xFFFFFEFF, or
sections of a
config.ini
Changes in MySQL Cluster configuration parameters do not take effect until the
Parameters".
process with the
ndbd
sources as
32 8
2 – 2 – 1.
file for configuring MySQL Cluster data nodes.
Nodes".
Cluster").
Section 17.3.3, "Overview of MySQL Cluster
1594
option.
--initial
and is equal to
MAX_INT_RNIL
Section 17.5.5,
[1619] option.
--initial
[ndbd]