3.3.4 The Ndb_logevent_type Type

Description.  These are the types of log events available in the MGM API, grouped by event category. (See Section 3.3.7, “The ndb_mgm_event_category Type”.)

Enumeration values.  Possible values are shown, along with descriptions, in the following table:

CategoryTypeDescription
NDB_MGM_EVENT_CATEGORY_CONNECTION(Connection events)
 NDB_LE_ConnectedThe node has connected
 NDB_LE_DisconnectedThe node was disconnected
 NDB_LE_CommunicationClosedCommunication with the node has been closed
 NDB_LE_CommunicationOpenedCommunication with the node has been started
 NDB_LE_ConnectedApiVersionThe API version used by an API node; in the case of a MySQL server (SQL node), this is the same as displayed by SELECT VERSION()
NDB_MGM_EVENT_CATEGORY_CHECKPOINT(Checkpoint events)
 NDB_LE_GlobalCheckpointStartedA global checkpoint has been started
 NDB_LE_GlobalCheckpointCompletedA global checkpoint has been completed
 NDB_LE_LocalCheckpointStartedThe node has begun a local checkpoint
 NDB_LE_LocalCheckpointCompletedThe node has completed a local checkpoint
 NDB_LE_LCPStoppedInCalcKeepGciThe lcoal checkpoint was aborted, but the last global checkpoint was preserved
 NDB_LE_LCPFragmentCompletedCopying of a table fragment was completed
NDB_MGM_EVENT_CATEGORY_STARTUP(Startup events)
 NDB_LE_NDBStartStartedThe node has begun to start
 NDB_LE_NDBStartCompletedThe node has completed the startup process
 NDB_LE_STTORRYRecievedThe node received an STTORRY signal, indicating that the reading of configuration data is underway; see Section 8.5.2, “Configuration Read Phase (STTOR Phase -1)”, and Section 8.5.3, “STTOR Phase 0”, for more information
 NDB_LE_StartPhaseCompletedA node start phase has been completed
 NDB_LE_CM_REGCONFThe node has received a CM_REGCONF signal; see Section 8.5.4, “STTOR Phase 1”, for more information
 NDB_LE_CM_REGREFThe node has received a CM_REGREF signal; see Section 8.5.4, “STTOR Phase 1”, for more information
 NDB_LE_FIND_NEIGHBOURSThe node has discovered its neighboring nodes in the cluster
 NDB_LE_NDBStopStartedThe node is beginning to shut down
 NDB_LE_NDBStopCompleted 
 NDB_LE_NDBStopForcedThe node is being forced to shut down (usually indicates a severe problem in the cluster)
 NDB_LE_NDBStopAbortedThe started to shut down, but was forced to continue running; this happens, for example, when a STOP command was issued in the management client for a node such that the cluster would no longer be able to keep all data available if the node were shut down
 NDB_LE_StartREDOLogRedo logging has been started
 NDB_LE_StartLogLogging has started
 NDB_LE_UNDORecordsExecutedThe node has read and executed all records from the redo log
 NDB_LE_StartReportThe node is issuing a start report
NDB_MGM_EVENT_CATEGORY_NODE_RESTART(Restart events)
 NDB_LE_NR_CopyDictThe node is copying the data dictionary
 NDB_LE_NR_CopyDistrThe node is copying data distribution information
 NDB_LE_NR_CopyFragsStartedThe node is copying table fragments
 NDB_LE_NR_CopyFragDoneThe node has completed copying a table fragment
 NDB_LE_NR_CopyFragsCompletedThe node has completed copying all necessary table fragments
NDB_MGM_EVENT_CATEGORY_NODE_RESTART(Node failure and arbitration)
 NDB_LE_NodeFailCompletedAll (remaining) nodes has been notified of the failure of a data node
 NDB_LE_NODE_FAILREPA data node has failed
 NDB_LE_ArbitStateThis event is used to report on the current state of arbitration in the cluster
 NDB_LE_ArbitResultThis event is used to report on the outcome of node arbitration
 NDB_LE_GCP_TakeoverStartedThe node is attempting to become the master node (to assume responsibility for GCPs)
 NDB_LE_GCP_TakeoverCompletedThe node has become the master (and assumed responsibility for GCPs)
 NDB_LE_LCP_TakeoverStartedThe node is attempting to become the master node (to assume responsibility for LCPs)
 NDB_LE_LCP_TakeoverCompletedThe node has become the master (and assumed responsibility for LCPs)
NDB_MGM_EVENT_CATEGORY_STATISTIC(Statistics events)
 NDB_LE_TransReportCountersThis indicates a report of transaction activity, which is given approximately once every 10 seconds
 NDB_LE_OperationReportCountersIndicates a report on the number of operations performed by this node (also provided approximately once every 10 seconds)
 NDB_LE_TableCreatedA new table has been created
 NDB_LE_UndoLogBlockedUndo logging is blocked because the log buffer is close to overflowing
 NDB_LE_JobStatistic 
 NDB_LE_SendBytesStatisticIndicates a report of the average number of bytes transmitted per send operation by this node
 NDB_LE_ReceiveBytesStatisticIndicates a report of the average number of bytes received per send operation to this node
 NDB_LE_MemoryUsageA DUMP 1000 command has been issued to this node, and it is reporting its memory usage in turn
NDB_MGM_EVENT_CATEGORY_ERROR(Errors and warnings)
 NDB_LE_TransporterErrorA transporter error has occurred; see Section 7.4, “NDB Transporter Errors”, for transporter error codes and messages
 NDB_LE_TransporterWarningA potential problem is occurring in the transporter; see Section 7.4, “NDB Transporter Errors”, for transporter error codes and messages
 NDB_LE_MissedHeartbeatIndicates a data node has missed a hreatbeat expected from another data node
 NDB_LE_DeadDueToHeartbeatA data node has missed at least 3 heartbeats in succssion from another data node, and is reporting that it can no longer communicate with that data node
 NDB_LE_WarningEventIndicates a warning message
NDB_MGM_EVENT_CATEGORY_INFO(Information events)
 NDB_LE_SentHeartbeatA node heartbeat has been sent
 NDB_LE_CreateLogBytes 
 NDB_LE_InfoEventIndicates an informational message
[Single-User Mode]NDB_LE_SingleUserThe cluster has entered or exited single user mode
 NDB_LE_EventBufferStatusThis type of event indicates potentially excessive usage of the event buffer
NDB_MGM_EVENT_CATEGORY_BACKUP(Backups)
 NDB_LE_BackupStartedA backup has been started
 NDB_LE_BackupFailedToStartA backup has failed to start
 NDB_LE_BackupCompletedA backup has been completed successfully
 NDB_LE_BackupAbortedA backup in progress was terminated by the user