Spec-Zone .ru
спецификации, руководства, описания, API
|
|
Spec-Zone .ru
спецификации, руководства, описания, API
|
The [ndb_mgmd] section is used to configure the behavior of the management server.
[mgm] can be used as an alias; the two section names are equivalent. All parameters
in the following list are optional and assume their default values if omitted.
If neither the ExecuteOnComputer nor the HostName
parameter is present, the default value localhost will be assumed for both.
| Effective Version | Type/Units | Default | Range/Values |
|---|---|---|---|
| NDB 7.3.0 | unsigned | [none] | 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 MySQL Cluster node, regardless of the type of node.
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 MySQL Cluster.
| Effective Version | Type/Units | Default | Range/Values |
|---|---|---|---|
| NDB 7.3.0 | unsigned | [none] | 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 MySQL Cluster node, regardless of the type of node.
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 MySQL
Cluster release.
This refers to the Id set for one of the computers defined in a [computer] section of the config.ini file.
This is the port number on which the management server listens for configuration requests and management commands.
| Effective Version | Type/Units | Default | Range/Values |
|---|---|---|---|
| NDB 7.3.0 | name or IP address | [none] | ... |
| Restart Type: S | |||
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.
| Effective Version | Type/Units | Default | Range/Values |
|---|---|---|---|
| NDB 7.3.0 | {CONSOLE|SYSLOG|FILE} | [see text] | ... |
| 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.
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 MySQL Cluster NDB 7.3, the default log file name used in such cases is
ndb_
(in some older versions, the log file's default name, used if nodeid_cluster.logFILE was specified without also setting filename, was logger.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_,
where node_id_cluster.log,maxsize=1000000,maxfiles=6node_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
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.
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.
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.
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).
This parameter is available beginning with MySQL Cluster NDB 6.4.0. It 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; the maxmimum is 4294967039. For more
detailed information about the behavior and use of TotalSendBufferMemory and configuring send buffer memory parameters,
see Section 17.3.2.12,
"Configuring MySQL Cluster Send Buffer Parameters".
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 MySQL 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
17.1.6.10, "Limitations Relating to Multiple MySQL Cluster Nodes".