Skip navigation links
15.5.4.3 Using CLUSTERLOG STATISTICS in the MySQL Cluster Management Client »
Section Navigation      [Toggle]

15.5.4.2. MySQL Cluster Log Events

An event report reported in the event logs has the following format: 

datetime [string] severity -- message

For example: 

09:19:30 2005-07-24 [NDB] INFO -- Node 4 Start phase 4 completed

This section discusses all reportable events, ordered by category and severity level within each category.

In the event descriptions, GCP and LCP mean “Global Checkpoint” and “Local Checkpoint,” respectively.

CONNECTION Events

These events are associated with connections between Cluster nodes.

Event Priority Severity Level Description
data nodes connected 8 INFO Data nodes connected
data nodes disconnected 8 INFO Data nodes disconnected
Communication closed 8 INFO SQL node or data node connection closed
Communication opened 8 INFO SQL node or data node connection opened

CHECKPOINT Events

The logging messages shown here are associated with checkpoints.

Event Priority Severity Level Description
LCP stopped in calc keep GCI 0 ALERT LCP stopped
Local checkpoint fragment completed 11 INFO LCP on a fragment has been completed
Global checkpoint completed 10 INFO GCP finished
Global checkpoint started 9 INFO Start of GCP: REDO log is written to disk
Local checkpoint completed 8 INFO LCP completed normally
Local checkpoint started 7 INFO Start of LCP: data written to disk
Report undo log blocked 7 INFO UNDO logging blocked; buffer near overflow

STARTUP Events

The following events are generated in response to the startup of a node or of the cluster and of its success or failure. They also provide information relating to the progress of the startup process, including information concerning logging activities.

Event Priority Severity Level Description
Internal start signal received STTORRY 15 INFO Blocks received after completion of restart
Undo records executed 15 INFO  
New REDO log started 10 INFO GCI keep X, newest restorable GCI Y
New log started 10 INFO Log part X, start MB Y, stop MB Z
Node has been refused for inclusion in the cluster 8 INFO Node cannot be included in cluster due to misconfiguration, inability to establish communication, or other problem
data node neighbors 8 INFO Shows neighboring data nodes
data node start phase X completed 4 INFO A data node start phase has been completed
Node has been successfully included into the cluster 3 INFO Displays the node, managing node, and dynamic ID
data node start phases initiated 1 INFO NDB Cluster nodes starting
data node all start phases completed 1 INFO NDB Cluster nodes started
data node shutdown initiated 1 INFO Shutdown of data node has commenced
data node shutdown aborted 1 INFO Unable to shut down data node normally

NODERESTART Events

The following events are generated when restarting a node and relate to the success or failure of the node restart process.

Event Priority Severity Level Description
Node failure phase completed 8 ALERT Reports completion of node failure phases
Node has failed, node state was X 8 ALERT Reports that a node has failed
Report arbitrator results 2 ALERT There are eight different possible results for arbitration attempts:

  • Arbitration check failed — less than 1/2 nodes left

  • Arbitration check succeeded — node group majority

  • Arbitration check failed — missing node group

  • Network partitioning — arbitration required

  • Arbitration succeeded — affirmative response from node X

  • Arbitration failed - negative response from node X

  • Network partitioning - no arbitrator available

  • Network partitioning - no arbitrator configured

Completed copying a fragment 10 INFO  
Completed copying of dictionary information 8 INFO  
Completed copying distribution information 8 INFO  
Starting to copy fragments 8 INFO  
Completed copying all fragments 8 INFO  
GCP takeover started 7 INFO  
GCP takeover completed 7 INFO  
LCP takeover started 7 INFO  
LCP takeover completed (state = X) 7 INFO  
Report whether an arbitrator is found or not 6 INFO There are seven different possible outcomes when seeking an arbitrator:

  • Management server restarts arbitration thread [state=X]

  • Prepare arbitrator node X [ticket=Y]

  • Receive arbitrator node X [ticket=Y]

  • Started arbitrator node X [ticket=Y]

  • Lost arbitrator node X - process failure [state=Y]

  • Lost arbitrator node X - process exit [state=Y]

  • Lost arbitrator node X <error msg> [state=Y]

STATISTICS Events

The following events are of a statistical nature. They provide information such as numbers of transactions and other operations, amount of data sent or received by individual nodes, and memory usage.

Event Priority Severity Level Description
Report job scheduling statistics 9 INFO Mean internal job scheduling statistics
Sent number of bytes 9 INFO Mean number of bytes sent to node X
Received # of bytes 9 INFO Mean number of bytes received from node X
Report transaction statistics 8 INFO Numbers of: transactions, commits, reads, simple reads, writes, concurrent operations, attribute information, and aborts
Report operations 8 INFO Number of operations
Report table create 7 INFO  
Memory usage 5 INFO Data and index memory usage (80%, 90%, and 100%)

ERROR Events

These events relate to Cluster errors and warnings. The presence of one or more of these generally indicates that a major malfunction or failure has occurred.

Event Priority Severity Description
Dead due to missed heartbeat 8 ALERT Node X declared “dead” due to missed heartbeat
Transporter errors 2 ERROR  
Transporter warnings 8 WARNING  
Missed heartbeats 8 WARNING Node X missed heartbeat #Y
General warning events 2 WARNING  

INFO Events

These events provide general information about the state of the cluster and activities associated with Cluster maintenance, such as logging and heartbeat transmission.

Event Priority Severity Description
Sent heartbeat 12 INFO Heartbeat sent to node X
Create log bytes 11 INFO Log part, log file, MB
General information events 2 INFO