MySQL Cluster Configuration Files
1587
Effective Version
Type/Units
Default
Range/Values
MySQL 5.0.0
bytes
64K
16K - 4G
Restart Type: N
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.
17.3.2.8. MySQL Cluster TCP/IP Connections Using Direct Connections
Setting up a cluster using direct connections between data nodes requires specifying explicitly
the crossover IP addresses of the data nodes so connected in the
[tcp]
section of the cluster
config.ini
file.
In the following example, we envision a cluster with at least four hosts, one each for a management
server, an SQL node, and two data nodes. The cluster as a whole resides on the
172.23.72.*
subnet of a LAN. In addition to the usual network connections, the two data nodes are connected
directly using a standard crossover cable, and communicate with one another directly using IP
addresses in the
1.1.0.*
address range as shown:
# Management Server
[ndb_mgmd]
Id=1
HostName=172.23.72.20
# SQL Node
[mysqld]
Id=2
HostName=172.23.72.21
# Data Nodes
[ndbd]
Id=3
HostName=172.23.72.22
[ndbd]
Id=4
HostName=172.23.72.23
# TCP/IP Connections
[tcp]
NodeId1=3
NodeId2=4
HostName1=1.1.0.1
HostName2=1.1.0.2
The
HostName1
[1585]
and
HostName2
[1586]
parameters are used only when specifying direct TCP
connections.
The use of direct TCP connections between data nodes can improve the cluster's overall efficiency
by enabling the data nodes to bypass an Ethernet device such as a switch, hub, or router, thus
cutting down on the cluster's latency. It is important to note that to take the best advantage of direct
connections in this fashion with more than two data nodes, you must have a direct connection between
each data node and every other data node in the same node group.
17.3.2.9. MySQL Cluster Shared-Memory Connections
MySQL Cluster attempts to use the shared memory transporter and configure it automatically where
possible. (In very early versions of MySQL Cluster, shared memory segments functioned only when
the server binary was built using
--with-ndb-shm
.)
[shm]
sections in the
config.ini
file explicitly
Содержание 5.0
Страница 1: ...MySQL 5 0 Reference Manual ...
Страница 18: ...xviii ...
Страница 60: ...40 ...
Страница 396: ...376 ...
Страница 578: ...558 ...
Страница 636: ...616 ...
Страница 844: ...824 ...
Страница 1234: ...1214 ...
Страница 1426: ...MySQL Proxy Scripting 1406 The following diagram shows an overview of the classes exposed by MySQL Proxy ...
Страница 1427: ...MySQL Proxy Scripting 1407 ...
Страница 1734: ...1714 ...
Страница 1752: ...1732 ...
Страница 1783: ...Configuring Connector ODBC 1763 ...
Страница 1793: ...Connector ODBC Examples 1773 ...
Страница 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Страница 1842: ...Connector Net Installation 1822 5 Once the installation has been completed click Finish to exit the installer ...
Страница 1864: ...Connector Net Visual Studio Integration 1844 Figure 20 24 Debug Stepping Figure 20 25 Function Stepping 1 of 2 ...
Страница 2850: ...2830 ...
Страница 2854: ...2834 ...
Страница 2928: ...2908 ...
Страница 3000: ...2980 ...
Страница 3122: ...3102 ...
Страница 3126: ...3106 ...
Страница 3174: ...3154 ...
Страница 3232: ...3212 ...