- MySQL 5.1 Reference Manual :: 17 MySQL Cluster NDB 6.X/7.X :: 17.5 Management of MySQL Cluster
-
- MySQL 5.1 Reference Manual
- Preface, Notes, Licenses
- 1 General Information
- 2 Installing and Upgrading MySQL
- 3 Tutorial
- 4 MySQL Programs
- 5 MySQL Server Administration
- 6 Backup and Recovery
- 7 Optimization
- 8 Language Structure
- 9 Internationalization and Localization
- 10 Data Types
- 11 Functions and Operators
- 12 SQL Statement Syntax
- 13 Storage Engines
- 14 High Availability and Scalability
- 15 MySQL Enterprise Monitor
- 16 Replication
- 17 MySQL Cluster NDB 6.X/7.X
- 18 Partitioning
- 19 Stored Programs and Views
- 20 INFORMATION_SCHEMA Tables
- 21 Connectors and APIs
- 22 Extending MySQL
- A MySQL 5.1 Frequently Asked Questions
- B Errors, Error Codes, and Common Problems
- C MySQL Change History
- D Restrictions and Limits
- Index
- Standard Index
- C Function Index
- Command Index
- Function Index
- INFORMATION_SCHEMA Index
- Transaction Isolation Level Index
- JOIN Types Index
- Operator Index
- Option Index
- Privileges Index
- SQL Modes Index
- Status Variable Index
- Statement/Syntax Index
- System Variable Index
[+/-]
- 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. Event Reports Generated in MySQL Cluster
- 17.5.5. MySQL Cluster Log Messages
- 17.5.6. MySQL Cluster Single User Mode
- 17.5.7. Quick Reference: MySQL Cluster SQL Statements
- 17.5.8. The
ndbinfo
MySQL Cluster Information Database - 17.5.9. MySQL Cluster Security Issues
- 17.5.10. MySQL Cluster Disk Data Tables
- 17.5.11. Adding MySQL Cluster Data Nodes Online
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.9, “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_
; this is usually found in the management server'snode_id
_cluster.logDataDir
directory, but this location can be overridden using theLogDestination
option—see Section 17.3.2.5, “Defining a MySQL Cluster Management Server”, for details. (Recall thatnode_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.Some aspects of the cluster's operation can be also be monitored from an SQL node using the
SHOW ENGINE NDB STATUS
statement. See Section 12.4.5.16, “SHOW ENGINE
Syntax”, for more information.In MySQL Cluster NDB 7.1.1 and later, detailed information about cluster operations is available in real time via an SQL interface using the
ndbinfo
database. For more information, see Section 17.5.8, “Thendbinfo
MySQL Cluster Information Database”.