[+/-]
In the sections that follow, we discuss known limitations in MySQL
5.1 Cluster and MySQL Cluster 5.1 Carrier Grade Edition releases as compared
with the features available when using the MyISAM
and InnoDB storage engines. Currently, there are
no plans to address these in coming releases of MySQL
5.1 or MySQL Cluster 5.1 Carrier Grade Edition; however, we will attempt to
supply fixes for these issues in subsequent release series. If you
check the “Cluster” category in the MySQL bugs database
at http://bugs.mysql.com, you can find known bugs
which (if marked “5.1”) we intend to
correct in upcoming releases of MySQL 5.1.
If you check the following categories under “MySQL Server:” in the MySQL bugs database at http://bugs.mysql.com, you can find known bugs which (if marked “5.1”) we intend to correct in upcoming releases of MySQL 5.1:
Cluster
Cluster Direct API (NDBAPI)
Cluster Disk Data
Cluster Replication
Some of these issues may be addressed in MySQL Cluster 5.1 Carrier Grade Edition and the fixes included in a future mainline MySQL Cluster version.
This information is intended to be complete with respect to the conditions just set forth. You can report any discrepancies that you encounter to the MySQL bugs database using the instructions given in Section 1.7, “How to Report Bugs or Problems”. If we do not plan to fix the problem in MySQL 5.1, we will add it to the list.
See Section 18.15.11, “Previous MySQL Cluster Issues Resolved in MySQL 5.1” for a list of issues in MySQL Cluster in MySQL 5.0 that have been resolved in the current version.
Limitations and other issues specific to MySQL Cluster Replication are described in Section 18.12.3, “Known Issues in MySQL Cluster Replication”.

User Comments
Add your own comment.