Documentation Home
MySQL 9.3 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 40.8Mb
PDF (A4) - 40.9Mb
Man Pages (TGZ) - 261.1Kb
Man Pages (Zip) - 368.3Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb


MySQL 9.3 Reference Manual  / ...  / MySQL NDB Cluster 9.3  / Management of NDB Cluster  / NDB Cluster Log Messages  /  NDB Cluster: Messages in the Cluster Log

25.6.2.1 NDB Cluster: Messages in the Cluster Log

The following table lists the most commonNDB cluster log messages. For information about the cluster log, log events, and event types, seeSection 25.6.3, “Event Reports Generated in NDB Cluster”. These log messages also correspond to log event types in the MGM API; seeThe Ndb_logevent_type Type, for related information of interest to Cluster API developers.

Table 25.25 Common NDB cluster log messages

Log MessageDescriptionEvent NameEvent TypePrioritySeverity
Nodemgm_node_id: Nodedata_node_id ConnectedThe data node having node IDnode_id has connected to the management server (nodemgm_node_id).ConnectedConnection8INFO
Nodemgm_node_id: Nodedata_node_id DisconnectedThe data node having node IDdata_node_id has disconnected from the management server (nodemgm_node_id).DisconnectedConnection8ALERT
Nodedata_node_id: Communication to Nodeapi_node_id closedThe API node or SQL node having node IDapi_node_id is no longer communicating with data nodedata_node_id.CommunicationClosedConnection8INFO
Nodedata_node_id: Communication to Nodeapi_node_id openedThe API node or SQL node having node IDapi_node_id is now communicating with data nodedata_node_id.CommunicationOpenedConnection8INFO
Nodemgm_node_id: Nodeapi_node_id: APIversionThe API node having node IDapi_node_id has connected to management nodemgm_node_id usingNDB API versionversion (generally the same as the MySQL version number).ConnectedApiVersionConnection8INFO
Nodenode_id: Global checkpointgci startedA global checkpoint with the IDgci has been started; nodenode_id is the master responsible for this global checkpoint.GlobalCheckpointStartedCheckpoint9INFO
Nodenode_id: Global checkpointgci completedThe global checkpoint having the IDgci has been completed; nodenode_id was the master responsible for this global checkpoint.GlobalCheckpointCompletedCheckpoint10INFO
Nodenode_id: Local checkpointlcp started. Keep GCI =current_gci oldest restorable GCI =old_gciThe local checkpoint having sequence IDlcp has been started on nodenode_id. The most recent GCI that can be used has the indexcurrent_gci, and the oldest GCI from which the cluster can be restored has the indexold_gci.LocalCheckpointStartedCheckpoint7INFO
Nodenode_id: Local checkpointlcp completedThe local checkpoint having sequence IDlcp on nodenode_id has been completed.LocalCheckpointCompletedCheckpoint8INFO
Nodenode_id: Local Checkpoint stopped in CALCULATED_KEEP_GCIThe node was unable to determine the most recent usable GCI.LCPStoppedInCalcKeepGciCheckpoint0ALERT
Nodenode_id: Table ID =table_id, fragmentID = fragment_id has completed LCP on Nodenode_id maxGciStarted:started_gci maxGciCompleted:completed_gciA table fragment has been checkpointed to disk on nodenode_id. The GCI in progress has the indexstarted_gci, and the most recent GCI to have been completed has the indexcompleted_gci.LCPFragmentCompletedCheckpoint11INFO
Nodenode_id: ACC Blockednum_1 and TUP Blockednum_2 times last secondUndo logging is blocked because the log buffer is close to overflowing.UndoLogBlockedCheckpoint7INFO
Nodenode_id: Start initiatedversionData nodenode_id, runningNDB versionversion, is beginning its startup process.NDBStartStartedStartUp1INFO
Nodenode_id: StartedversionData nodenode_id, runningNDB versionversion, has started successfully.NDBStartCompletedStartUp1INFO
Nodenode_id: STTORRY received after restart finishedThe node has received a signal indicating that a cluster restart has completed.STTORRYRecievedStartUp15INFO
Nodenode_id: Start phasephase completed (type)The node has completed start phasephase of atype start. For a listing of start phases, seeSection 25.6.4, “Summary of NDB Cluster Start Phases”. (type is one ofinitial,system,node,initial node, or<Unknown>.)StartPhaseCompletedStartUp4INFO
Nodenode_id: CM_REGCONF president =president_id, own Node =own_id, our dynamic id =dynamic_idNodepresident_id has been selected as“president”.own_id anddynamic_id should always be the same as the ID (node_id) of the reporting node.CM_REGCONFStartUp3INFO
Nodenode_id: CM_REGREF from Nodepresident_id to our Nodenode_id. Cause =causeThe reporting node (IDnode_id) was unable to accept nodepresident_id as president. Thecause of the problem is given as one ofBusy,Election with wait = false,Not president,Election without selecting new candidate, orNo such cause.CM_REGREFStartUp8INFO
Nodenode_id: We are Nodeown_id with dynamic IDdynamic_id, our left neighbor is Nodeid_1, our right is Nodeid_2The node has discovered its neighboring nodes in the cluster (nodeid_1 and nodeid_2).node_id,own_id, anddynamic_id should always be the same; if they are not, this indicates a serious misconfiguration of the cluster nodes.FIND_NEIGHBOURSStartUp8INFO
Nodenode_id:type shutdown initiatedThe node has received a shutdown signal. Thetype of shutdown is eitherCluster orNode.NDBStopStartedStartUp1INFO
Nodenode_id: Node shutdown completed[,action] [Initiated by signalsignal.]The node has been shut down. This report may include anaction, which if present is one ofrestarting,no start, orinitial. The report may also include a reference to anNDB Protocolsignal; for possible signals, refer toOperations and Signals.NDBStopCompletedStartUp1INFO
Nodenode_id: Forced node shutdown completed[, action]. [Occurred during startphasestart_phase.] [ Initiated bysignal.] [Caused by errorerror_code: 'error_message(error_classification).error_status'. [(extra infoextra_code)]]The node has been forcibly shut down. Theaction (one ofrestarting,no start, orinitial) subsequently being taken, if any, is also reported. If the shutdown occurred while the node was starting, the report includes thestart_phase during which the node failed. If this was a result of asignal sent to the node, this information is also provided (seeOperations and Signals, for more information). If the error causing the failure is known, this is also included; for more information aboutNDB error messages and classifications, seeNDB Cluster API Errors.NDBStopForcedStartUp1ALERT
Nodenode_id: Node shutdown abortedThe node shutdown process was aborted by the user.NDBStopAbortedStartUp1INFO
Nodenode_id: StartLog: [GCI Keep:keep_pos LastCompleted:last_pos NewestRestorable:restore_pos]This reports global checkpoints referenced during a node start. The redo log prior tokeep_pos is dropped.last_pos is the last global checkpoint in which data node the participated;restore_pos is the global checkpoint which is actually used to restore all data nodes.StartREDOLogStartUp4INFO
startup_message [Listed separately; see below.]There are a number of possible startup messages that can be logged under different circumstances. These are listed separately; seeSection 25.6.2.2, “NDB Cluster Log Startup Messages”.StartReportStartUp4INFO
Nodenode_id: Node restart completed copy of dictionary informationCopying of data dictionary information to the restarted node has been completed.NR_CopyDictNodeRestart8INFO
Nodenode_id: Node restart completed copy of distribution informationCopying of data distribution information to the restarted node has been completed.NR_CopyDistrNodeRestart8INFO
Nodenode_id: Node restart starting to copy the fragments to Nodenode_idCopy of fragments to starting data nodenode_id has begunNR_CopyFragsStartedNodeRestart8INFO
Nodenode_id: Table ID =table_id, fragment ID =fragment_id have been copied to Nodenode_idFragmentfragment_id from tabletable_id has been copied to data nodenode_idNR_CopyFragDoneNodeRestart10INFO
Nodenode_id: Node restart completed copying the fragments to Nodenode_idCopying of all table fragments to restarting data nodenode_id has been completedNR_CopyFragsCompletedNodeRestart8INFO
Nodenode_id: Nodenode1_id completed failure of Nodenode2_idData nodenode1_id has detected the failure of data nodenode2_idNodeFailCompletedNodeRestart8ALERT
All nodes completed failure of Nodenode_idAll (remaining) data nodes have detected the failure of data nodenode_idNodeFailCompletedNodeRestart8ALERT
Node failure ofnode_idblock completedThe failure of data nodenode_id has been detected in theblockNDB kernel block, where block is 1 ofDBTC,DBDICT,DBDIH, orDBLQH; for more information, seeNDB Kernel BlocksNodeFailCompletedNodeRestart8ALERT
Nodemgm_node_id: Nodedata_node_id has failed. The Node state at failure wasstate_codeA data node has failed. Its state at the time of failure is described by an arbitration state codestate_code: possible state code values can be found in the fileinclude/kernel/signaldata/ArbitSignalData.hpp.NODE_FAILREPNodeRestart8ALERT
President restarts arbitration thread [state=state_code] orPrepare arbitrator nodenode_id [ticket=ticket_id] orReceive arbitrator nodenode_id [ticket=ticket_id] orStarted arbitrator nodenode_id [ticket=ticket_id] orLost arbitrator nodenode_id - process failure [state=state_code] orLost arbitrator nodenode_id - process exit [state=state_code] orLost arbitrator nodenode_id -error_message [state=state_code]This is a report on the current state and progress of arbitration in the cluster.node_id is the node ID of the management node or SQL node selected as the arbitrator.state_code is an arbitration state code, as found ininclude/kernel/signaldata/ArbitSignalData.hpp. When an error has occurred, anerror_message, also defined inArbitSignalData.hpp, is provided.ticket_id is a unique identifier handed out by the arbitrator when it is selected to all the nodes that participated in its selection; this is used to ensure that each node requesting arbitration was one of the nodes that took part in the selection process.ArbitStateNodeRestart6INFO
Arbitration check lost - less than 1/2 nodes left orArbitration check won - all node groups and more than 1/2 nodes left orArbitration check won - node group majority orArbitration check lost - missing node group orNetwork partitioning - arbitration required orArbitration won - positive reply from nodenode_id orArbitration lost - negative reply from nodenode_id orNetwork partitioning - no arbitrator available orNetwork partitioning - no arbitrator configured orArbitration failure -error_message [state=state_code]This message reports on the result of arbitration. In the event of arbitration failure, anerror_message and an arbitrationstate_code are provided; definitions for both of these are found ininclude/kernel/signaldata/ArbitSignalData.hpp.ArbitResultNodeRestart2ALERT
Nodenode_id: GCP Take over startedThis node is attempting to assume responsibility for the next global checkpoint (that is, it is becoming the master node)GCP_TakeoverStartedNodeRestart7INFO
Nodenode_id: GCP Take over completedThis node has become the master, and has assumed responsibility for the next global checkpointGCP_TakeoverCompletedNodeRestart7INFO
Nodenode_id: LCP Take over startedThis node is attempting to assume responsibility for the next set of local checkpoints (that is, it is becoming the master node)LCP_TakeoverStartedNodeRestart7INFO
Nodenode_id: LCP Take over completedThis node has become the master, and has assumed responsibility for the next set of local checkpointsLCP_TakeoverCompletedNodeRestart7INFO
Nodenode_id: Trans. Count =transactions, Commit Count =commits, Read Count =reads, Simple Read Count =simple_reads, Write Count =writes, AttrInfo Count =AttrInfo_objects, Concurrent Operations =concurrent_operations, Abort Count =aborts, Scans =scans, Range scans =range_scansThis report of transaction activity is given approximately once every 10 secondsTransReportCountersStatistic8INFO
Nodenode_id: Operations=operationsNumber of operations performed by this node, provided approximately once every 10 secondsOperationReportCountersStatistic8INFO
Nodenode_id: Table with ID =table_id createdA table having the table ID shown has been createdTableCreatedStatistic7INFO
Nodenode_id: Mean loop Counter in doJob last 8192 times =countJobStatisticStatistic9INFO
Mean send size to Node =node_id last 4096 sends =bytes bytesThis node is sending an average ofbytes bytes per send to nodenode_idSendBytesStatisticStatistic9INFO
Mean receive size to Node =node_id last 4096 sends =bytes bytesThis node is receiving an average ofbytes of data each time it receives data from nodenode_idReceiveBytesStatisticStatistic9INFO
Nodenode_id: Data usage isdata_memory_percentage% (data_pages_used 32K pages of totaldata_pages_total) /Nodenode_id: Index usage isindex_memory_percentage% (index_pages_used 8K pages of totalindex_pages_total)This report is generated when aDUMP 1000 command is issued in the cluster management clientMemoryUsageStatistic5INFO
Nodenode1_id: Transporter to nodenode2_id reported errorerror_code:error_messageA transporter error occurred while communicating with nodenode2_id; for a listing of transporter error codes and messages, seeNDB Transporter Errors, inMySQL NDB Cluster Internals ManualTransporterErrorError2ERROR
Nodenode1_id: Transporter to nodenode2_id reported errorerror_code:error_messageA warning of a potential transporter problem while communicating with nodenode2_id; for a listing of transporter error codes and messages, seeNDB Transporter Errors, for more informationTransporterWarningError8WARNING
Nodenode1_id: Nodenode2_id missed heartbeatheartbeat_idThis node missed a heartbeat from nodenode2_idMissedHeartbeatError8WARNING
Nodenode1_id: Nodenode2_id declared dead due to missed heartbeatThis node has missed at least 3 heartbeats from nodenode2_id, and so has declared that node“dead”DeadDueToHeartbeatError8ALERT
Nodenode1_id: Node Sent Heartbeat to node =node2_idThis node has sent a heartbeat to nodenode2_idSentHeartbeatInfo12INFO
Nodenode_id: Event buffer status (object_id): used=bytes_used (percent_used% of alloc) alloc=bytes_allocated max=bytes_available latest_consumed_epoch=latest_consumed_epoch latest_buffered_epoch=latest_buffered_epoch report_reason=report_reasonThis 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 buffered and consumed epochs; for more information, seeSection 25.6.2.3, “Event Buffer Reporting in the Cluster Log”EventBufferStatus2Info7INFO
Nodenode_id: Entering single user mode,Nodenode_id: Entered single user mode NodeAPI_node_id has exclusive access,Nodenode_id: Entering single user modeThese reports are written to the cluster log when entering and exiting single user mode;API_node_id is the node ID of the API or SQL having exclusive access to the cluster (for more information, seeSection 25.6.6, “NDB Cluster Single User Mode”); the messageUnknown single user reportAPI_node_id indicates an error has taken place and should never be seen in normal operationSingleUserInfo7INFO
Nodenode_id: Backupbackup_id started from nodemgm_node_idA backup has been started using the management node havingmgm_node_id; this message is also displayed in the cluster management client when theSTART BACKUP command is issued; for more information, seeSection 25.6.8.2, “Using The NDB Cluster Management Client to Create a Backup”BackupStartedBackup7INFO
Nodenode_id: Backupbackup_id started from nodemgm_node_id completed. StartGCP:start_gcp StopGCP:stop_gcp #Records:records #LogRecords:log_records Data:data_bytes bytes Log:log_bytes bytesThe backup having the IDbackup_id has been completed; for more information, seeSection 25.6.8.2, “Using The NDB Cluster Management Client to Create a Backup”BackupCompletedBackup7INFO
Nodenode_id: Backup request frommgm_node_id failed to start. Error:error_codeThe backup failed to start; for error codes, seeMGM API ErrorsBackupFailedToStartBackup7ALERT
Nodenode_id: Backupbackup_id started frommgm_node_id has been aborted. Error:error_codeThe backup was terminated after starting, possibly due to user interventionBackupAbortedBackup7ALERT