Oracle 5.0 Reference Manual page 1608

define shared-memory connections between nodes in the cluster. When explicitly defining shared
memory as the connection method, it is necessary to define at least NodeId1,
All other parameters have default values that should work well in most cases.
Important
SHM functionality is considered experimental only. It is not officially supported
in any current MySQL Cluster release, and testing results indicate that SHM
performance is not appreciably greater than when using TCP/IP for the
transporter.
For these reasons, you must determine for yourself or by using our free
resources (forums, mailing lists) whether SHM can be made to work correctly in
your specific case.
•
NodeId1
Effective Version
MySQL 5.0.0
Restart Type: N
NodeId2
Effective Version
MySQL 5.0.0
Restart Type: N
To identify a connection between two nodes it is necessary to provide node identifiers for each of
them, as and NodeId2.
NodeId1
•
HostName1
Effective Version
MySQL 5.0.0
Restart Type: N
HostName2
Effective Version
MySQL 5.0.0
Restart Type: N
The and
HostName1
be used for a given SHM connection between two nodes. The values used for these parameters can
be hostnames or IP addresses.
•
ShmKey
Effective Version
MySQL 5.0.0
Restart Type: N
When setting up shared memory segments, a node ID, expressed as an integer, is used to identify
uniquely the shared memory segment to use for the communication. There is no default value.
•
ShmSize
MySQL Cluster Configuration Files
Type/Units
numeric
Type/Units
numeric
Type/Units
name or IP address
Type/Units
name or IP address
parameters can be used to specify specific network interfaces to
HostName2
Type/Units
unsigned
1588
Default
[none]
Default
[none]
Default
[none]
Default
[none]
Default
[none]
and ShmKey.
NodeId2
Range/Values
...
Range/Values
...
Range/Values
...
Range/Values
...
Range/Values
0 - 4G