ndbinfo: The NDB Cluster Information Database Restart completed [none] Initial state Status numbers 0 through 12 apply on master nodes only; the remainder of those shown in the table apply to all restarting data nodes. Status numbers 13 and 14 define node failure states; 20 and 21 occur when no information about the restart of a given node is available. See also Section 23.5.4, “Summary of NDB Cluster Start Phases” . The  server_locks  table is similar in structure to the  cluster_locks  table, and provides a subset of the information found in the latter table, but which is specific to the SQL node (MySQL server) where it resides. (The  cluster_locks  table provides information about all locks in the cluster.) More precisely, server_locks  contains information about locks requested by threads belonging to the current  mysqld instance, and serves as a companion table to  server_operations . This may be useful for correlating locking patterns with specific MySQL user sessions, queries, or use cases. The  server_locks  table contains the following columns: MySQL connection ID ID of reporting node ID of reporting LDM instance ID of table containing this row ID of fragment containing locked row ID of locked row Transaction ID Lock request mode 4578 • mode • transid • rowid • fragmentid • tableid • block_instance • node_id • mysql_connection_id • 21  ( NODE_NOT_RESTARTED_YET ) • 20  ( NOT_DEFINED_IN_CLUSTER ) 23.5.14.44 The ndbinfo server_locks Table