Some database objects such as tables and indexes have different
limitations when using the
NDBCLUSTER storage engine:
Table names containing special characters.
NDB tables whose names
contain characters other than letters, numbers, dashes,
and underscores and which are created on one SQL node were
not always discovered correctly by other SQL nodes. (Bug
#31470)
This issue was fixed in MySQL 5.1.23, MySQL Cluster NDB 6.2.7, and MySQL Cluster NDB 6.3.4.
Number of database objects.
The maximum number of all
NDB database objects in a
single MySQL Cluster—including databases, tables,
and indexes—is limited to 20320.
Attributes per table. Prior to MySQL Cluster NDB 7.0.15 and MySQL Cluster NDB 7.1.4, the maximum number of attributes (that is, columns and indexes) per table is limited to 128.
Beginning with MySQL Cluster NDB 7.0.15 and MySQL Cluster NDB 7.1.4, this limit is increased to 512.
Attributes per key. The maximum number of attributes per key is 32.
Row size.
Prior to MySQL Cluster NDB 7.0, the maximum permitted size
of any one row was 8052 bytes; in MySQL Cluster NDB 7.0
and later, this is 14000 bytes. Each
BLOB or
TEXT column contributes 256
+ 8 = 264 bytes to this total.
Number of rows per partition. A single MySQL Cluster partition can hold a maximum of 46137488 rows. Since the number of partitions is the same as the number of data nodes in the cluster (see Section 16.1.2, “MySQL Cluster Nodes, Node Groups, Replicas, and Partitions”), you can increase the available space for data storage by using more data nodes.
In MySQL Cluster NDB 7.0 and later MySQL Cluster release series, you can increase the number of data nodes in the cluster while the cluster remains in operation. See Section 16.5.12, “Adding MySQL Cluster Data Nodes Online”, for more information.
It is also possible to increase the number of partitions for
NDB tables by using explicit
KEY or LINEAR KEY
partitioning (see Section 17.2.4, “KEY Partitioning”).

User Comments
Add your own comment.