- 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
The following are limitations specific to the
NDBCLUSTER storage engine:
Machine architecture. All machines used in the cluster must have the same architecture. That is, all machines hosting nodes must be either big-endian or little-endian, and you cannot use a mixture of both. For example, you cannot have a management node running on a PowerPC which directs a data node that is running on an x86 machine. This restriction does not apply to machines simply running mysql or other clients that may be accessing the cluster's SQL nodes.
-
Binary logging. MySQL Cluster has the following limitations or restrictions with regard to binary logging:
sql_log_binhas no effect on data operations; however, it is supported for schema operations.MySQL Cluster cannot produce a binlog for tables having
BLOBcolumns but no primary key.-
Only the following schema operations are logged in a cluster binlog which is not on the mysqld executing the statement:
See also Section 17.1.5.10, “Limitations Relating to Multiple MySQL Cluster Nodes”.
User Comments
Add your own comment.