Documentation Home
MySQL 8.0 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 43.2Mb
PDF (A4) - 43.3Mb
Man Pages (TGZ) - 296.4Kb
Man Pages (Zip) - 401.7Kb
Info (Gzip) - 4.3Mb
Info (Zip) - 4.3Mb
Excerpts from this Manual

25.4.3.8 Defining the System

The [system] section is used for parameters applying to the cluster as a whole. The Name system parameter is used with MySQL Enterprise Monitor; ConfigGenerationNumber and PrimaryMGMNode are not used in production environments. Except when using NDB Cluster with MySQL Enterprise Monitor, is not necessary to have a [system] section in the config.ini file.

More information about these parameters can be found in the following list:

  • ConfigGenerationNumber

    Version (or later) NDB 8.0.13
    Type or units unsigned
    Default 0
    Range 0 - 4294967039 (0xFFFFFEFF)
    Restart Type

    Node Restart: Requires a rolling restart of the cluster. (NDB 8.0.13)

    Configuration generation number. This parameter is currently unused.

  • Name

    Version (or later) NDB 8.0.13
    Type or units string
    Default [...]
    Range ...
    Restart Type

    Node Restart: Requires a rolling restart of the cluster. (NDB 8.0.13)

    Set a name for the cluster. This parameter is required for deployments with MySQL Enterprise Monitor; it is otherwise unused.

    You can obtain the value of this parameter by checking the Ndb_system_name status variable. In NDB API applications, you can also retrieve it using get_system_name().

  • PrimaryMGMNode

    Version (or later) NDB 8.0.13
    Type or units unsigned
    Default 0
    Range 0 - 4294967039 (0xFFFFFEFF)
    Restart Type

    Node Restart: Requires a rolling restart of the cluster. (NDB 8.0.13)

    Node ID of the primary management node. This parameter is currently unused.

Restart types.  Information about the restart types used by the parameter descriptions in this section is shown in the following table:

Table 25.19 NDB Cluster restart types

Symbol Restart Type Description
N Node The parameter can be updated using a rolling restart (see Section 25.6.5, “Performing a Rolling Restart of an NDB Cluster”)
S System All cluster nodes must be shut down completely, then restarted, to effect a change in this parameter
I Initial Data nodes must be restarted using the --initial option