MySQL Cluster Configuration Files
1589
Effective Version
Type/Units
Default
Range/Values
MySQL 5.0.0
bytes
1M
64K - 4G
Restart Type: N
Each SHM connection has a shared memory segment where messages between nodes are placed
by the sender and read by the reader. The size of this segment is defined by
ShmSize
. The default
value is 1MB.
•
SendSignalId
Effective Version
Type/Units
Default
Range/Values
MySQL 5.0.0
boolean
false
true, false
Restart Type: N
To retrace the path of a distributed message, it is necessary to provide each message with a unique
identifier. Setting this parameter to
Y
causes these message IDs to be transported over the network
as well. This feature is disabled by default in production builds, and enabled in
-debug
builds.
•
Checksum
Effective Version
Type/Units
Default
Range/Values
MySQL 5.0.0
boolean
true
true, false
Restart Type: N
This parameter is a boolean (
Y
/
N
) parameter which is disabled by default. When it is enabled,
checksums for all messages are calculated before being placed in the send buffer.
This feature prevents messages from being corrupted while waiting in the send buffer. It also serves
as a check against data being corrupted during transport.
•
SigNum
Effective Version
Type/Units
Default
Range/Values
MySQL 5.0.0
unsigned
[none]
0 - 4G
Restart Type: N
When using the shared memory transporter, a process sends an operating system signal to the other
process when there is new data available in the shared memory. Should that signal conflict with with
an existing signal, this parameter can be used to change it. This is a possibility when using SHM due
to the fact that different operating systems use different signal numbers.
The default value of
SigNum
is 0; therefore, it must be set to avoid errors in the cluster log when
using the shared memory transporter. Typically, this parameter is set to 10 in the
[shm default]
section of the
config.ini
file.
17.3.2.10. SCI Transport Connections in MySQL Cluster
[sci]
sections in the
config.ini
file explicitly define SCI (Scalable Coherent Interface) connections
between cluster nodes. Using SCI transporters in MySQL Cluster is supported only when the MySQL
binaries are built using
--with-ndb-sci=/your/path/to/SCI
. The
path
should point to a
directory that contains at a minimum
lib
and
include
directories containing SISCI libraries and
header files. (See
Section 17.3.5, “Using High-Speed Interconnects with MySQL Cluster”
for more
information about SCI.)
In addition, SCI requires specialized hardware.
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...