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.
Version Introduced | 4.1.3 | |
Restart Type | node | |
Permitted Values (>= 4.1.3) | ||
Type | numeric |
|
Default |
|
|
Range | 1-63 |
Each node in the cluster has a unique identity, which is represented by an integer value in the range 1 to 63 inclusive. This ID is used by all internal cluster messages for addressing the node.
This parameter can also be written as
NodeId
, although the short form is
sufficient (and preferred for this reason).
Version Introduced | 4.1.3 | |
Restart Type | system | |
Permitted Values (>= 4.1.3) | ||
Type | string |
|
Default |
|
|
Range | - |
This refers to the Id
set for one of the
computers defined in a [computer]
section
of the config.ini
file.
Version Introduced | 4.1.3 | |
Restart Type | node | |
Permitted Values (>= 4.1.3, <= 4.1.7) | ||
Type | numeric |
|
Default | 2200 |
|
Range | 0-64K |
|
Permitted Values (>= 4.1.8) | ||
Type | numeric |
|
Default | 1186 |
|
Range | 0-64K |
This is the port number on which the management server listens for configuration requests and management commands.
Version Introduced | 4.1.3 | |
Restart Type | system | |
Permitted Values (>= 4.1.3) | ||
Type | string |
|
Default |
|
|
Range | - |
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.
Version Introduced | 4.1.3 | |
Restart Type | node | |
Permitted Values (>= 4.1.3) | ||
Type | string |
|
Default | FILE:filename=ndb_nodeid_cluster.log,maxsize=1000000,maxfiles=6 |
|
Range | - |
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.
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
Version Introduced | 4.1.3 | |
Restart Type | node | |
Permitted Values (>= 4.1.3) | ||
Type | numeric |
|
Default | 1 |
|
Range | 0-2 |
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).
Version Introduced | 4.1.3 | |
Restart Type | node | |
Permitted Values (>= 4.1.3) | ||
Type | numeric |
|
Default | 0 |
|
Range | 0-4G |
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.
Version Introduced | 4.1.3 | |
Restart Type | node | |
Permitted Values | ||
Type | string |
|
Default | . |
|
Range | - |
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.
After making changes in a management node's configuration, it is necessary to perform a rolling restart of the cluster in order 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 15.1.4.9, “Limitations Relating to Multiple MySQL Cluster Nodes”.
User Comments
Add your own comment.