Description:
The maximum number of API nodes is documented in an inconsequential way.
From http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-limitations-resolved.html
-->
Maximum number of cluster nodes. Prior to MySQL Cluster NDB 6.1.1, the total maximum number of nodes in a MySQL Cluster was 63, including all SQL nodes (MySQL Servers), API nodes (applications accessing the cluster other than MySQL servers), data nodes, and management servers.
Starting with MySQL Cluster NDB 6.1.1, up to 255 API nodes (including MySQL servers acting as cluster SQL nodes) are supported by a single cluster. The total number of data nodes and management nodes beginning with this version is 63, of which up to 48 can be data nodes.
Note
The limitation that a data node cannot have a node ID greater than 49 continues to apply.
-->
From http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-api-definition.html
-->
Id
The Id value is used to identify the node in all cluster internal messages. It must be an integer in the range 1 to 63 inclusive, and must be unique among all node IDs within the cluster.
-->
From http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-limitations-limits.html
-->
Node and data object maximums. The following limits apply to numbers of cluster nodes and metadata objects:
*
The maximum number of data nodes is 48.
A data node must have a node ID in the range of 1‐49, inclusive. (Management and API nodes may use any integer in the range of 1‐63 inclusive as a node ID.)
*
The total maximum number of nodes in a MySQL Cluster is 63. This number includes all SQL nodes (MySQL Servers), API nodes (applications accessing the cluster other than MySQL servers), data nodes, and management servers.
*
The maximum number of metadata objects in current versions of MySQL Cluster. This limit is hard-coded.
-->
How to repeat:
Read the manual.
Suggested fix:
Fix the manual.
