This documentation is for an older version. If you're using the most current version, select the documentation for that version with the version switch in the upper right corner of the online documentation, or by downloading a newer PDF or EPUB file.

17.5 Management of MySQL Cluster

17.5.1 Summary of MySQL Cluster Start Phases
17.5.2 Commands in the MySQL Cluster Management Client
17.5.3 Online Backup of MySQL Cluster
17.5.4 MySQL Server Usage for MySQL Cluster
17.5.5 Performing a Rolling Restart of a MySQL Cluster
17.5.6 Event Reports Generated in MySQL Cluster
17.5.7 MySQL Cluster Log Messages
17.5.8 MySQL Cluster Single User Mode
17.5.9 Quick Reference: MySQL Cluster SQL Statements
17.5.10 MySQL Cluster Security Issues

Managing a MySQL Cluster involves a number of tasks, the first of which is to configure and start MySQL Cluster. This is covered in Section 17.3, “MySQL Cluster Configuration”, and Section 17.4, “MySQL Cluster Programs”.

The next few sections cover the management of a running MySQL Cluster.

For information about security issues relating to management and deployment of a MySQL Cluster, see Section 17.5.10, “MySQL Cluster Security Issues”.

There are essentially two methods of actively managing a running MySQL Cluster. The first of these is through the use of commands entered into the management client whereby cluster status can be checked, log levels changed, backups started and stopped, and nodes stopped and started. The second method involves studying the contents of the cluster log ndb_node_id_cluster.log; this is usually found in the management server's DataDir directory, but this location can be overridden using the LogDestination option—see Section, “Defining a MySQL Cluster Management Server”, for details. (Recall that node_id represents the unique identifier of the node whose activity is being logged.) The cluster log contains event reports generated by ndbd. It is also possible to send cluster log entries to a Unix system log.

In addition, some aspects of the cluster's operation can be monitored from an SQL node using the SHOW ENGINE NDB STATUS statement. See Section, “SHOW ENGINE Syntax”, for more information.