Event Reports Generated in NDB Cluster Table 23.64 Backup events Event Priority Severity Level Description BackupStarted 7 INFO Backup started BackupStatus 7 INFO Backup status BackupCompleted 7 INFO Backup completed BackupFailedToStart 7 ALERT Backup failed to start BackupAborted 7 ALERT Backup aborted by user RestoreStarted 7 INFO Started restoring from backup RestoreMetaData 7 INFO Restoring metadata RestoreData 7 INFO Restoring data RestoreLog 7 INFO Restoring log files RestoreCompleted 7 INFO Completed restoring from backup SavedEvent 7 INFO Event saved 23.5.3.3 Using CLUSTERLOG STATISTICS in the NDB Cluster Management Client The  NDB  management client’s  CLUSTERLOG STATISTICS  command can provide a number of useful statistics in its output. Counters providing information about the state of the cluster are updated at 5- second reporting intervals by the transaction coordinator (TC) and the local query handler (LQH), and written to the cluster log. Transaction coordinator statistics.   Each transaction has one transaction coordinator, which is chosen by one of the following methods: •In a round-robin fashion •By communication proximity •By supplying a data placement hint when the transaction is started Note You can determine which TC selection method is used for transactions started from a given SQL node using the  ndb_optimized_node_selection  system variable. All operations within the same transaction use the same transaction coordinator, which reports the following statistics: • Trans count.   This is the number transactions started in the last interval using this TC as the transaction coordinator. Any of these transactions may have committed, have been aborted, or remain uncommitted at the end of the reporting interval. • Commit count.   This is the number of transactions using this TC as the transaction coordinator that were committed in the last reporting interval. Because some transactions committed in this reporting Note Transactions do not migrate between TCs. 4472