- 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
Disk Data object maxmimums and minimums. Disk data objects are subject to the following maximums and minimums:
Maximum number of tablespaces: 232 (4294967296)
Maximum number of data files per tablespace: 216 (65535)
The theoretical maximum number of extents per tablespace data file is 216 (65525); however, for practical purposes, the recommended maximum number of extents per data file is 28 (32768).
-
Maximum data file size: The theoretical limit is 64G; however, in MySQL 5.1 (including MySQL Cluster NDB 6.X and 7.X through 7.1), the practical upper limit is 32G. This is equivalent to 32768 extents of 1M each.
The minimum and maximum possible sizes of extents for tablespace data files are 32K and 2G, respectively. See Section 12.1.18, “
CREATE TABLESPACESyntax”, for more information.
Disk Data tables and diskless mode. Use of Disk Data tables is not supported when running the cluster in diskless mode. Beginning with MySQL 5.1.12, it is disallowed altogether. (Bug#20008)
User Comments
Add your own comment.