Documentation Home
MySQL NDB Cluster 7.3-7.4
Related Documentation Download this Excerpt

MySQL NDB Cluster 7.3-7.4  /  Management of NDB Cluster

Chapter 7 Management of NDB Cluster

Table of Contents

7.1 Commands in the NDB Cluster Management Client
7.2 NDB Cluster Log Messages
7.2.1 NDB Cluster: Messages in the Cluster Log
7.2.2 NDB Cluster Log Startup Messages
7.2.3 NDB Cluster: NDB Transporter Errors
7.3 Event Reports Generated in NDB Cluster
7.3.1 NDB Cluster Logging Management Commands
7.3.2 NDB Cluster Log Events
7.3.3 Using CLUSTERLOG STATISTICS in the NDB Cluster Management Client
7.4 Summary of NDB Cluster Start Phases
7.5 Performing a Rolling Restart of an NDB Cluster
7.6 NDB Cluster Single User Mode
7.7 Adding NDB Cluster Data Nodes Online
7.7.1 Adding NDB Cluster Data Nodes Online: General Issues
7.7.2 Adding NDB Cluster Data Nodes Online: Basic procedure
7.7.3 Adding NDB Cluster Data Nodes Online: Detailed Example
7.8 Online Backup of NDB Cluster
7.8.1 NDB Cluster Backup Concepts
7.8.2 Using The NDB Cluster Management Client to Create a Backup
7.8.3 Configuration for NDB Cluster Backups
7.8.4 NDB Cluster Backup Troubleshooting
7.9 MySQL Server Usage for NDB Cluster
7.10 NDB Cluster Disk Data Tables
7.10.1 NDB Cluster Disk Data Objects
7.10.2 Using Symbolic Links with Disk Data Objects
7.10.3 NDB Cluster Disk Data Storage Requirements
7.11 Online Operations with ALTER TABLE in NDB Cluster
7.12 Distributed Privileges Using Shared Grant Tables
7.13 NDB API Statistics Counters and Variables
7.14 ndbinfo: The NDB Cluster Information Database
7.14.1 The ndbinfo arbitrator_validity_detail Table
7.14.2 The ndbinfo arbitrator_validity_summary Table
7.14.3 The ndbinfo blocks Table
7.14.4 The ndbinfo cluster_operations Table
7.14.5 The ndbinfo cluster_transactions Table
7.14.6 The ndbinfo config_params Table
7.14.7 The ndbinfo counters Table
7.14.8 The ndbinfo dict_obj_types Table
7.14.9 The ndbinfo disk_write_speed_base Table
7.14.10 The ndbinfo disk_write_speed_aggregate Table
7.14.11 The ndbinfo disk_write_speed_aggregate_node Table
7.14.12 The ndbinfo diskpagebuffer Table
7.14.13 The ndbinfo logbuffers Table
7.14.14 The ndbinfo logspaces Table
7.14.15 The ndbinfo membership Table
7.14.16 The ndbinfo memoryusage Table
7.14.17 The ndbinfo memory_per_fragment Table
7.14.18 The ndbinfo nodes Table
7.14.19 The ndbinfo operations_per_fragment Table
7.14.20 The ndbinfo resources Table
7.14.21 The ndbinfo restart_info Table
7.14.22 The ndbinfo server_operations Table
7.14.23 The ndbinfo server_transactions Table
7.14.24 The ndbinfo tc_time_track_stats Table
7.14.25 The ndbinfo threadblocks Table
7.14.26 The ndbinfo threadstat Table
7.14.27 The ndbinfo transporters Table
7.15 Quick Reference: NDB Cluster SQL Statements
7.16 NDB Cluster Security Issues
7.16.1 NDB Cluster Security and Networking Issues
7.16.2 NDB Cluster and MySQL Privileges
7.16.3 NDB Cluster and MySQL Security Procedures

Managing an NDB Cluster involves a number of tasks, the first of which is to configure and start NDB Cluster. This is covered in Chapter 5, Configuration of NDB Cluster, and Chapter 6, NDB Cluster Programs.

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

For information about security issues relating to management and deployment of an NDB Cluster, see Section 7.16, “NDB Cluster Security Issues”.

There are essentially two methods of actively managing a running NDB 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. (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.

Some aspects of the cluster's operation can be also be monitored from an SQL node using the SHOW ENGINE NDB STATUS statement.

More detailed information about NDB Cluster operations is available in real time through an SQL interface using the ndbinfo database. For more information, see Section 7.14, “ndbinfo: The NDB Cluster Information Database”.

NDB statistics counters provide improved monitoring using the mysql client. These counters, implemented in the NDB kernel, relate to operations performed by or affecting Ndb objects, such as starting, closing, and aborting transactions; primary key and unique key operations; table, range, and pruned scans; blocked threads waiting for various operations to complete; and data and events sent and received by NDB Cluster. The counters are incremented by the NDB kernel whenever NDB API calls are made or data is sent to or received by the data nodes.

mysqld exposes the NDB API statistics counters as system status variables, which can be identified from the prefix common to all of their names (Ndb_api_). The values of these variables can be read in the mysql client from the output of a SHOW STATUS statement, or by querying either the SESSION_STATUS table or the GLOBAL_STATUS table (in the INFORMATION_SCHEMA database). By comparing the values of the status variables before and after the execution of an SQL statement that acts on NDB tables, you can observe the actions taken on the NDB API level that correspond to this statement, which can be beneficial for monitoring and performance tuning of NDB Cluster.

MySQL Cluster Manager provides an advanced command-line interface that simplifies many otherwise complex NDB Cluster management tasks, such as starting, stopping, or restarting an NDB Cluster with a large number of nodes. The MySQL Cluster Manager client also supports commands for getting and setting the values of most node configuration parameters as well as mysqld server options and variables relating to NDB Cluster. See MySQL™ Cluster Manager 1.4.8 User Manual, for more information.