- 5.5 MySQL Cluster Log Messages
- 5.5.1 MySQL Cluster — Messages in the Cluster Log
- 5.5.2 MySQL Cluster — NDB Transporter Errors
The following table lists the most common
NDB cluster log messages. For
information about the cluster log, log events, and event types,
see Section 5.4, “Event Reports Generated in MySQL Cluster”. These log
messages also correspond to log event types in the MGM API; see
The Ndb_logevent_type Type, for related information
of interest to Cluster API developers.
|
Log Message.
Description.
The data node having node ID
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
The data node having node ID
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
The API node or SQL node having node ID
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
The API node or SQL node having node ID
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
The API node having node ID
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
A global checkpoint with the ID
|
Event Name.
Event Type.
Priority. 9 Severity.
|
|
Log Message.
Description.
The global checkpoint having the ID
|
Event Name.
Event Type.
Priority. 10 Severity.
|
|
Log Message.
Description.
The local checkpoint having sequence ID
|
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description.
The local checkpoint having sequence ID
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description. The node was unable to determine the most recent usable GCI. |
Event Name.
Event Type.
Priority. 0 Severity.
|
|
Log Message.
Description.
A table fragment has been checkpointed to disk on
node |
Event Name.
Event Type.
Priority. 11 Severity.
|
|
Log Message.
Description. Undo logging is blocked because the log buffer is close to overflowing. |
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description.
Data node |
Event Name.
Event Type.
Priority. 1 Severity.
|
|
Log Message.
Description.
Data node |
Event Name.
Event Type.
Priority. 1 Severity.
|
|
Log Message.
Description. The node has received a signal indicating that a cluster restart has completed. |
Event Name.
Event Type.
Priority. 15 Severity.
|
|
Log Message.
Description.
The node has completed start phase
|
Event Name.
Event Type.
Priority. 4 Severity.
|
|
Log Message.
Description.
Node |
Event Name.
Event Type.
Priority. 3 Severity.
|
|
Log Message.
Description.
The reporting node (ID
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
The node has discovered its neighboring nodes in the
cluster (node |
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
The node has received a shutdown signal. The
|
Event Name.
Event Type.
Priority. 1 Severity.
|
|
Log Message.
Description.
The node has been shut down. This report may include
an |
Event Name.
Event Type.
Priority. 1 Severity.
|
|
Log Message.
Description.
The node has been forcibly shut down. The
|
Event Name.
Event Type.
Priority. 1 Severity.
|
|
Log Message.
Description. The node shutdown process was aborted by the user. |
Event Name.
Event Type.
Priority. 1 Severity.
|
|
Log Message.
Description.
This reports global checkpoints referenced during a
node start. The redo log prior to
|
Event Name.
Event Type.
Priority. 4 Severity.
|
|
Log Message.
Description. There are a number of possible startup messages that can be logged under different circumstances. |
Event Name.
Event Type.
Priority. 4 Severity.
|
|
Log Message.
Description. Copying of data dictionary information to the restarted node has been completed. |
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description. Copying of data distribution information to the restarted node has been completed. |
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
Copy of fragments to starting data node
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
Fragment |
Event Name.
Event Type.
Priority. 10 Severity.
|
|
Log Message.
Description.
Copying of all table fragments to restarting data
node |
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message. Any of the following:
Description. One of the following (each corresponding to the same-numbered message listed above):
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
A data node has failed. Its state at the time of
failure is described by an arbitration state code
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
This is a report on the current state and progress
of arbitration in the cluster.
|
Event Name.
Event Type.
Priority. 6 Severity.
|
|
Log Message.
Description.
This message reports on the result of arbitration.
In the event of arbitration failure, an
|
Event Name.
Event Type.
Priority. 2 Severity.
|
|
Log Message.
Description. This node is attempting to assume responsibility for the next global checkpoint (that is, it is becoming the master node) |
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description. This node has become the master, and has assumed responsibility for the next global checkpoint |
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description. This node is attempting to assume responsibility for the next set of local checkpoints (that is, it is becoming the master node) |
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description. This node has become the master, and has assumed responsibility for the next set of local checkpoints |
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description. This report of transaction activity is given approximately once every 10 seconds |
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description. Number of operations performed by this node, provided approximately once every 10 seconds |
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description. A table having the table ID shown has been created |
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description. |
Event Name.
Event Type.
Priority. 9 Severity.
|
|
Log Message.
Description.
This node is sending an average of
|
Event Name.
Event Type.
Priority. 9 Severity.
|
|
Log Message.
Description.
This node is receiving an average of
|
Event Name.
Event Type.
Priority. 9 Severity.
|
|
Log Message.
Description.
This report is generated when a |
Event Name.
Event Type.
Priority. 5 Severity.
|
|
Log Message.
Description.
A transporter error occurred while communicating
with node |
Event Name.
Event Type.
Priority. 2 Severity.
|
|
Log Message.
Description.
A warning of a potential transporter problem while
communicating with node
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
This node missed a heartbeat from node
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
This node has missed at least 3 heartbeats from node
|
Event Name.
Event Type.
Priority. 8 Severity.
|
|
Log Message.
Description.
This node has sent a heartbeat to node
|
Event Name.
Event Type.
Priority. 12 Severity.
|
|
Log Message.
Description. This report is seen during heavy event buffer usage, for example, when many updates are being applied in a relatively short period of time; the report shows the number of bytes and the percentage of event buffer memory used, the bytes allocated and percentage still available, and the latest and latest restorable global checkpoints |
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description.
These reports are written to the cluster log when
entering and exiting single user mode;
|
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description.
A backup has been started using the management node
having |
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description.
The backup having the ID
|
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description.
The backup failed to start; for error codes, see
MGM |
Event Name.
Event Type.
Priority. 7 Severity.
|
|
Log Message.
Description. The backup was terminated after starting, possibly due to user intervention |
Event Name.
Event Type.
Priority. 7 Severity.
|
