Documentation Home
MySQL 5.5 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 27.2Mb
PDF (A4) - 27.2Mb
PDF (RPM) - 25.8Mb
HTML Download (TGZ) - 6.5Mb
HTML Download (Zip) - 6.6Mb
HTML Download (RPM) - 5.6Mb
Man Pages (TGZ) - 158.5Kb
Man Pages (Zip) - 262.1Kb
Info (Gzip) - 2.6Mb
Info (Zip) - 2.6Mb
Excerpts from this Manual

MySQL 5.5 Reference Manual  /  ...  /  Defining an NDB Cluster Management Server

18.3.3.5 Defining an NDB Cluster Management Server

The [ndb_mgmd] section is used to configure the behavior of the management server. If multiple management servers are employed, you can specify parameters common to all of them in an [ndb_mgmd default] section. [mgm] and [mgm default] are older aliases for these, supported for backward compatibility.

All parameters in the following list are optional and assume their default values if omitted.

Note

If neither the ExecuteOnComputer nor the HostName parameter is present, the default value localhost will be assumed for both.

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

Table 18.9 NDB Cluster restart types

Symbol Restart Type Description
N Node The parameter can be updated using a rolling restart (see Section 18.5.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

  • Id

    Table 18.10 This table provides type and value information for the Id management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units unsigned
    Default [none]
    Range 1 - 255
    Restart Type IS

    Each node in the cluster has a unique identity. For a management node, this is represented by an integer value in the range 1 to 255, inclusive. This ID is used by all internal cluster messages for addressing the node, and so must be unique for each NDB Cluster node, regardless of the type of node.

    Note

    Data node IDs must be less than 49. If you plan to deploy a large number of data nodes, it is a good idea to limit the node IDs for management nodes (and API nodes) to values greater than 48.

    The use of the Id parameter for identifying management nodes is deprecated in favor of NodeId. Although Id continues to be supported for backward compatibility, it now generates a warning and is subject to removal in a future version of NDB Cluster.

  • NodeId

    Table 18.11 This table provides type and value information for the NodeId management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units unsigned
    Default [none]
    Range 1 - 255
    Restart Type IS

    Each node in the cluster has a unique identity. For a management node, this is represented by an integer value in the range 1 to 255 inclusive. This ID is used by all internal cluster messages for addressing the node, and so must be unique for each NDB Cluster node, regardless of the type of node.

    Note

    Data node IDs must be less than 49. If you plan to deploy a large number of data nodes, it is a good idea to limit the node IDs for management nodes (and API nodes) to values greater than 48.

    NodeId is the preferred parameter name to use when identifying management nodes. Although the older Id continues to be supported for backward compatibility, it is now deprecated and generates a warning when used; it is also subject to removal in a future NDB Cluster release.

  • ExecuteOnComputer

    Table 18.12 This table provides type and value information for the ExecuteOnComputer management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units name
    Default [none]
    Range ...
    Restart Type S

    This refers to the Id set for one of the computers defined in a [computer] section of the config.ini file.

  • PortNumber

    Table 18.13 This table provides type and value information for the PortNumber management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units unsigned
    Default 1186
    Range 0 - 64K
    Restart Type S

    This is the port number on which the management server listens for configuration requests and management commands.

  • HostName

    Table 18.14 This table provides type and value information for the HostName management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units name or IP address
    Default [none]
    Range ...
    Restart Type N

    Specifying this parameter defines the hostname of the computer on which the management node is to reside. To specify a hostname other than localhost, either this parameter or ExecuteOnComputer is required.

  • LogDestination

    Table 18.15 This table provides type and value information for the LogDestination management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units {CONSOLE|SYSLOG|FILE}
    Default [see text]
    Range ...
    Restart Type N

    This parameter specifies where to send cluster logging information. There are three options in this regard—CONSOLE, SYSLOG, and FILE—with FILE being the default:

    • CONSOLE outputs the log to stdout:

      CONSOLE
    • SYSLOG sends the log to a syslog facility, possible values being one of auth, authpriv, cron, daemon, ftp, kern, lpr, mail, news, syslog, user, uucp, local0, local1, local2, local3, local4, local5, local6, or local7.

      Note

      Not every facility is necessarily supported by every operating system.

      SYSLOG:facility=syslog
    • FILE pipes the cluster log output to a regular file on the same machine. The following values can be specified:

      • filename: The name of the log file.

        In NDB 7.2.6 and earlier, the log file's default name, used if FILE was specified without also setting filename, was logger.log. Beginning with NDB 7.2.7, the default log file name used in such cases is ndb_nodeid_cluster.log.

      • maxsize: The maximum size (in bytes) to which the file can grow before logging rolls over to a new file. When this occurs, the old log file is renamed by appending .N to the file name, where N is the next number not yet used with this name.

      • maxfiles: The maximum number of log files.

      FILE:filename=cluster.log,maxsize=1000000,maxfiles=6

      The default value for the FILE parameter is FILE:filename=ndb_node_id_cluster.log,maxsize=1000000,maxfiles=6, where node_id is the ID of the node.

    It is possible to specify multiple log destinations separated by semicolons as shown here:

    CONSOLE;SYSLOG:facility=local0;FILE:filename=/var/log/mgmd
  • ArbitrationRank

    Table 18.16 This table provides type and value information for the ArbitrationRank management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units 0-2
    Default 1
    Range 0 - 2
    Restart Type N

    This parameter is used to define which nodes can act as arbitrators. Only management nodes and SQL nodes can be arbitrators. ArbitrationRank can take one of the following values:

    • 0: The node will never be used as an arbitrator.

    • 1: The node has high priority; that is, it will be preferred as an arbitrator over low-priority nodes.

    • 2: Indicates a low-priority node which be used as an arbitrator only if a node with a higher priority is not available for that purpose.

    Normally, the management server should be configured as an arbitrator by setting its ArbitrationRank to 1 (the default for management nodes) and those for all SQL nodes to 0 (the default for SQL nodes).

    You can disable arbitration completely either by setting ArbitrationRank to 0 on all management and SQL nodes, or by setting the Arbitration parameter in the [ndbd default] section of the config.ini global configuration file. Setting Arbitration causes any settings for ArbitrationRank to be disregarded.

  • ArbitrationDelay

    Table 18.17 This table provides type and value information for the ArbitrationDelay management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units milliseconds
    Default 0
    Range 0 - 4294967039 (0xFFFFFEFF)
    Restart Type N

    An integer value which causes the management server's responses to arbitration requests to be delayed by that number of milliseconds. By default, this value is 0; it is normally not necessary to change it.

  • DataDir

    Table 18.18 This table provides type and value information for the DataDir management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units path
    Default .
    Range ...
    Restart Type N

    This specifies the directory where output files from the management server will be placed. These files include cluster log files, process output files, and the daemon's process ID (PID) file. (For log files, this location can be overridden by setting the FILE parameter for LogDestination as discussed previously in this section.)

    The default value for this parameter is the directory in which ndb_mgmd is located.

  • PortNumberStats

    Table 18.19 This table provides type and value information for the PortNumberStats management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units unsigned
    Default [none]
    Range 0 - 64K
    Restart Type N

    This parameter specifies the port number used to obtain statistical information from an NDB Cluster management server. It has no default value.

  • Wan

    Table 18.20 This table provides type and value information for the wan management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units boolean
    Default false
    Range true, false
    Restart Type N

    Use WAN TCP setting as default.

  • HeartbeatThreadPriority

    Table 18.21 This table provides type and value information for the HeartbeatThreadPriority management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units string
    Default [none]
    Range ...
    Restart Type S

    Set the scheduling policy and priority of heartbeat threads for management and API nodes.

    The syntax for setting this parameter is shown here:

    HeartbeatThreadPriority = policy[, priority]
    
    policy:
      {FIFO | RR}

    When setting this parameter, you must specify a policy. This is one of FIFO (first in, first out) or RR (round robin). The policy value is followed optionally by the priority (an integer).

  • ExtraSendBufferMemory

    Table 18.22 This table provides type and value information for the ExtraSendBufferMemory management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.14
    Type or units bytes
    Default 0
    Range 0 - 32G
    Restart Type N

    This parameter specifies the amount of transporter send buffer memory to allocate in addition to any that has been set using TotalSendBufferMemory, SendBufferMemory, or both.

    This parameter was added in NDB 7.2.14. (Bug #14555359)

  • TotalSendBufferMemory

    Table 18.23 This table provides type and value information for the TotalSendBufferMemory management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.1
    Type or units bytes
    Default 0
    Range 256K - 4294967039 (0xFFFFFEFF)
    Restart Type N

    This parameter is used to determine the total amount of memory to allocate on this node for shared send buffer memory among all configured transporters.

    If this parameter is set, its minimum permitted value is 256KB; 0 indicates that the parameter has not been set. For more detailed information, see Section 18.3.3.13, “Configuring NDB Cluster Send Buffer Parameters”.

  • HeartbeatIntervalMgmdMgmd

    Table 18.24 This table provides type and value information for the HeartbeatIntervalMgmdMgmd management node configuration parameter

    Property Value
    Version (or later) NDB 7.2.12
    Type or units milliseconds
    Default 1500
    Range 100 - 4294967039 (0xFFFFFEFF)
    Restart Type N

    Specify the interval between heartbeat messages used to determine whether another management node is on contact with this one. The management node waits after 3 of these intervals to declare the connection dead; thus, the default setting of 1500 milliseconds causes the management node to wait for approximately 1600 ms before timing out.

    This parameter was added in NDB 7.2.12. (Bug #16426805, Bug #17807768)

Note

After making changes in a management node's configuration, it is necessary to perform a rolling restart of the cluster for the new configuration to take effect.

To add new management servers to a running NDB Cluster, it is also necessary to perform a rolling restart of all cluster nodes after modifying any existing config.ini files. For more information about issues arising when using multiple management nodes, see Section 18.1.7.10, “Limitations Relating to Multiple NDB Cluster Nodes”.


User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.