NDB Cluster Configuration Files in the send buffer. This feature ensures that messages are not corrupted while waiting in the send buffer, or by the transport mechanism. When  ndb_optimized_node_selection  is enabled, node proximity is used in some cases to select which node to connect to. This parameter can be used to influence proximity by setting it to a lower value, which is interpreted as “closer” . See the description of the system variable for more information. • Group • HostName1 The  HostName1  and  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 host names or IP addresses. Version (or later) NDB 8.0.13 Type or units name or IP address Default [...] Range ... Restart Type N (NDB 8.0.13) Version (or later) NDB 8.0.13 Type or units name or IP address Default [...] Range ... Restart Type N (NDB 8.0.13) • HostName2 • NodeId1 The  HostName1  and  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 host names or IP addresses. To identify a connection between two nodes it is necessary to provide their node IDs in the  [tcp] section of the configuration file as the values of  NodeId1  and  NodeId2 . These are the same unique  Id values for each of these nodes as described in Section 23.3.3.7, “Defining SQL and Other API Nodes in an NDB Cluster” . • NodeId2 Version (or later) NDB 8.0.13 Type or units numeric Default [none] Range 1 - 255 Restart Type N (NDB 8.0.13) Version (or later) NDB 8.0.13 Type or units numeric 4221