content_image/774559.jpg content_image/774552.jpg content_image/774551.jpg content_image/774557.jpg
NodeId  is the preferred parameter name to use when identifying API nodes. ( Id  continues to be supported for backward compatibility, but is now deprecated and generates a warning when used. It is also subject to future removal.) 

• ConnectionMap 

<img src='content_image/774559.jpg'>

Specifies which data nodes to connect. 

• NodeId 

<img src='content_image/774552.jpg'>

The NodeId  is an integer value used to identify the node in all cluster internal messages. The permitted range of values is 1 to 255 inclusive. This value must be unique for each node in the cluster, regardless of the type of node. 

<img src='content_image/774551.jpg'>

## Note 

In NDB 8.0.18 and later, data node IDs must be less than 145. If you plan to deploy a large number of data nodes, it is a good idea to limit the node IDs for API nodes (and management nodes) to values greater than 144. (Previous to NDB 8.0.18, the maximum supported value for a data node ID was 48.) 

NodeId  is the preferred parameter name to use when identifying management nodes. An alias, Id , was used for this purpose in very old versions of NDB Cluster, and continues to be supported for backward compatibility; it is now deprecated and generates a warning when used, and is subject to removal in a future release of NDB Cluster. 

• ExecuteOnComputer 

<img src='content_image/774557.jpg'>

