TCP/IP is the default transport mechanism for all connections between nodes in a MySQL Cluster. Normally it is not necessary to define TCP/IP connections; MySQL Cluster automatically sets up such connections for all data nodes, management nodes, and SQL or API nodes.
For an exception to this rule, see Section 188.8.131.52, “MySQL Cluster TCP/IP Connections Using Direct Connections”.
To override the default connection parameters, it is necessary
to define a connection using one or more
[tcp] sections in the
config.ini file. Each
[tcp] section explicitly defines a TCP/IP
connection between two MySQL Cluster nodes, and must contain at
a minimum the parameters
NodeId2, as well as any connection parameters
It is also possible to change the default values for these
parameters by setting them in the
[tcp] sections in the
config.ini file should be listed
last, following all other sections in the
file. However, this is not required for a
default] section. This requirement is a known issue
with the way in which the
is read by the MySQL Cluster management server.
Connection parameters which can be set in
sections of the
config.ini file are listed
To identify a connection between two nodes it is necessary
to provide their node IDs in the
section of the configuration file. These are the same unique
Id values for each of these nodes as
described in Section 184.108.40.206, “Defining SQL and Other API Nodes in a MySQL Cluster”.
HostName2 parameters can be used to
specify specific network interfaces to be used for a given
TCP connection between two nodes. The values used for these
parameters can be hostnames or IP addresses.
TCP transporters use a buffer to store all messages before performing the send call to the operating system. When this buffer reaches 64KB its contents are sent; these are also sent when a round of messages have been executed. To handle temporary overload situations it is also possible to define a bigger send buffer.
The default size of the send buffer is 256 KB; 2MB is recommended in most situations in which it is necessary to set this parameter. The minimum size is 64 KB; the theoretical maximum is 4 GB.
|MySQL 5.0.0||boolean||[see text]||true, false|
|Restart Type: N|
To be able to retrace a distributed message datagram, it is
necessary to identify each message. When this parameter is
Y, message IDs are transported
over the network. This feature is disabled by default in
production builds, and enabled in
This parameter is a boolean parameter (enabled by setting it
1, disabled by
setting it to
It is disabled by default. When it is enabled, checksums for
all messages are calculated before they placed in the send
buffer. This feature ensures that messages are not corrupted
while waiting in the send buffer, or by the transport
This formerly specified the port number to be used for listening for connections from other nodes. This parameter should no longer be used.
Specifies the size of the buffer used when receiving data from the TCP/IP socket.
The default value of this parameter from its of 64 KB; 1M is recommended in most situations where the size of the receive buffer needs to be set. The minimum possible value is 16K; theoretical maximum is 4G.