- 17.1.5 Known Limitations of MySQL Cluster
- 17.1.5.1 Noncompliance with SQL Syntax in MySQL Cluster
- 17.1.5.2 Limits and Differences of MySQL Cluster from Standard MySQL Limits
- 17.1.5.3 Limits Relating to Transaction Handling in MySQL Cluster
- 17.1.5.4 MySQL Cluster Error Handling
- 17.1.5.5 Limits Associated with Database Objects in MySQL Cluster
- 17.1.5.6 Unsupported or Missing Features in MySQL Cluster
- 17.1.5.7 Limitations Relating to Performance in MySQL Cluster
- 17.1.5.8 Issues Exclusive to MySQL Cluster
- 17.1.5.9 Limitations Relating to MySQL Cluster Disk Data Storage
- 17.1.5.10 Limitations Relating to Multiple MySQL Cluster Nodes
- 17.1.5.11 Previous MySQL Cluster Issues Resolved in MySQL 5.1, MySQL Cluster NDB 6.x, and MySQL Cluster NDB 7.x
Some database objects such as tables and indexes have different
limitations when using the
NDBCLUSTER storage engine:
-
Table names containing special characters.
NDBtables 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)Note
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
NDBdatabase objects in a single MySQL Cluster — including databases, tables, and indexes — is limited to 20320.Attributes per table. The maximum number of attributes (that is, columns and indexes) per table is limited to 128.
Attributes per key. The maximum number of attributes per key is 32.
Row size. The maximum permitted size of any one row is 8052 bytes. Each
BLOBorTEXTcolumn contributes 256 + 8 = 264 bytes towards this total.
User Comments
Add your own comment.