This section describes limitations relating to MySQL Cluster functionality that is unsupported or curtailed by MySQL Cluster Manager 1.1.6.
MySQL Cluster Manager and replication. MySQL Cluster Manager currently does not provide any explicit support for MySQL Cluster Replication. However, you should still be able to perform manual setup of replication of a MySQL Cluster that is managed by MySQL Cluster Manager.
Backup and restore operations.
MySQL Cluster Manager does not currently provide any integrated backup or
restore functionality. You can back up
NDB databases and tables using the
ndb_mgm client START
BACKUP command, and restore them using the ndb_restore
program. Both of these programs are supplied with the MySQL
Cluster distribution. For more information, see
Online Backup of MySQL Cluster, and
ndb_restore — Restore a MySQL Cluster Backup.
Because of this, configuration attribute changes which require a system initial restart currently cannot be made using MySQL Cluster Manager after a cluster is started for the first time, since this type of restart removes all cluster data and thus requires a complete backup and restore of the cluster. For information about restart types required for individual configuration attributes, see Appendix C, Attribute Summary Tables.
Backups of tables using storage engines other than
NDB, as well as of all other
database objects which are not tables, must be made using some
other method, such as mysqldump. (See
mysqldump — A Database Backup Program.)
Rolling restarts. Currently, all cluster nodes must be running in order to perform a rolling restart using MySQL Cluster Manager. However, MySQL Cluster itself requires only that at least one management server and all data nodes are running (in other words, any mysqld processes and any additional ndb_mgmd processes can be stopped). In such cases, you can perform the rolling restart manually, after stopping the MySQL Cluster Manager agent.
When making changes in configuration attributes only those nodes
requiring a restart to make the change take effect are actually
restarted. ndbapi nodes are never restarted by
MySQL Cluster Manager.
Cluster upgrades and downgrades. Not all upgrades and downgrades between different versions of MySQL Cluster are supported. (This is not an issue with MySQL Cluster Manager but rather a limitation in the MySQL Cluster software.) For information on supported online upgrades and downgrades, see Upgrading and Downgrading MySQL Cluster.
© 2013, Oracle Corporation and/or its affiliates