Oracle 5.0 Reference Manual page 1549

• Only the following schema operations are logged in a cluster binlog which is not on the
executing the statement:
•
CREATE TABLE
•
ALTER TABLE
•
DROP TABLE
•
CREATE DATABASE
•
DROP DATABASE
See also Section 17.1.5.9, "Limitations Relating to Multiple MySQL Cluster
17.1.5.9. Limitations Relating to Multiple MySQL Cluster Nodes
Multiple SQL nodes.
The following are issues relating to the use of multiple MySQL servers as MySQL Cluster SQL nodes,
and are specific to the
• No distributed table locks.
issued; no other SQL node in the cluster "sees" this lock. This is also true for a lock issued by any
statement that locks tables as part of its operations. (See next item for an example.)
•
ALTER TABLE
servers (SQL nodes). (As discussed in the previous item, MySQL Cluster does not support
distributed table locks.)
• Replication.
servers. However, if the database partitioning scheme is done at the application level and no
transactions take place across these partitions, replication can be made to work.
• Database autodiscovery.
servers accessing the same MySQL Cluster. However, autodiscovery of tables is supported in such
cases. What this means is that after a database named
MySQL server, you should issue a
MySQL server that accesses the same MySQL Cluster. (As of MySQL 5.0.2, you may also use
CREATE SCHEMA
be able to detect the database tables without error.
• DDL operations.
data node failures. If a data node fails while trying to perform one of these, the data dictionary is
locked and no further DDL statements can be executed without restarting the cluster.
Multiple management nodes.
When using multiple management servers:
• You must give nodes explicit IDs in connectstrings because automatic allocation of node IDs does
not work across multiple management servers.
In addition, all API nodes (including MySQL servers acting as SQL nodes), should list all
management servers using the same order in their connectstrings.
• You must take extreme care to have the same configurations for all management servers. No special
checks for this are performed by the cluster.
• Prior to MySQL 5.0.14, all data nodes had to be restarted after bringing up the cluster for the
management nodes to be able to see one another.
(See Bug #12307 and Bug #13070 for more information.)
Known Limitations of MySQL Cluster
/
CREATE SCHEMA
/
DROP SCHEMA
storage engine:
NDBCLUSTER
A
LOCK TABLES
operations.
ALTER TABLE
MySQL replication will not work correctly if updates are done on multiple MySQL
Autodiscovery of databases is not supported for multiple MySQL
CREATE DATABASE db_name
db_name.) Once this has been done for a given MySQL server, that server should
DDL operations (such as
works only for the SQL node on which the lock is
is not fully locking when running multiple MySQL
db_name
or
CREATE TABLE
1529
Nodes".
is created or imported using one
statement on each additional
TABLE) are not safe from
ALTER
mysqld