content_image/797353.jpg content_image/797357.jpg content_image/797358.jpg content_image/797354.jpg content_image/797355.jpg content_image/797356.jpg
<img src='content_image/797353.jpg'>

## 23.3.3.7 Defining SQL and Other API Nodes in an NDB Cluster 

The [mysqld]  and [api]  sections in the config.ini  file define the behavior of the MySQL servers (SQL nodes) and other applications (API nodes) used to access cluster data. None of the parameters shown is required. If no computer or host name is provided, any host can use this SQL or API node. 

Generally speaking, a [mysqld]  section is used to indicate a MySQL server providing an SQL interface to the cluster, and an [api]  section is used for applications other than mysqld  processes accessing cluster data, but the two designations are actually synonymous; you can, for instance, list parameters for a MySQL server acting as an SQL node in an [api]  section. 

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

• Id 

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

## Note 

For a discussion of MySQL server options for NDB Cluster, see MySQL Server Options for NDB Cluster. For information about MySQL server system variables relating to NDB Cluster, see NDB Cluster System Variables. 

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

The Id  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/797355.jpg'>

<img src='content_image/797356.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.) 

