- 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
Starting, stopping, or restarting a node may give rise to temporary errors causing some transactions to fail. These include the following cases:
Temporary errors. When first starting a node, it is possible that you may see Error 1204 Temporary failure, distribution changed and similar temporary errors.
Errors due to node failure. The stopping or failure of any data node can result in a number of different node failure errors. (However, there should be no aborted transactions when performing a planned shutdown of the cluster.)
In either of these cases, any errors that are generated must be handled within the application. This should be done by retrying the transaction.
See also Section 17.1.5.2, “Limits and Differences of MySQL Cluster from Standard MySQL Limits”.
User Comments
Add your own comment.