Performance Schema Lock Tables • Definition of table has changed in NDB Dictionary • Failed to setup binlogging for table • data_locks : Data locks held and requested • data_lock_waits : Relationships between data lock owners and data lock requestors blocked by those owners • metadata_locks : Metadata locks held and requested • table_handles : Table locks held and requested 5022 27.12.13.1 The data_locks Table 27.12.13 Performance Schema Lock Tables This list is not necessarily exhaustive, and is subject to change in future  NDB  releases. The  ndb_sync_excluded_objects  table was added in NDB 8.0.21. The Performance Schema exposes lock information through these tables: The following sections describe these tables in more detail. The  data_locks  table shows data locks held and requested. For information about which lock requests are blocked by which held locks, see Section 27.12.13.2, “The data_lock_waits Table” . Example data lock information: mysql>  SELECT * FROM performance_schema.data_locks\G *************************** 1. row *************************** ENGINE: INNODB ENGINE_LOCK_ID: 139664434886512:1059:139664350547912 ENGINE_TRANSACTION_ID: 2569 THREAD_ID: 46 EVENT_ID: 12 OBJECT_SCHEMA: test OBJECT_NAME: t1 PARTITION_NAME: NULL SUBPARTITION_NAME: NULL INDEX_NAME: NULL OBJECT_INSTANCE_BEGIN: 139664350547912 LOCK_TYPE: TABLE LOCK_MODE: IX LOCK_STATUS: GRANTED LOCK_DATA: NULL *************************** 2. row *************************** ENGINE: INNODB ENGINE_LOCK_ID: 139664434886512:2:4:1:139664350544872 ENGINE_TRANSACTION_ID: 2569 THREAD_ID: 46 EVENT_ID: 12 OBJECT_SCHEMA: test OBJECT_NAME: t1 PARTITION_NAME: NULL SUBPARTITION_NAME: NULL INDEX_NAME: GEN_CLUST_INDEX OBJECT_INSTANCE_BEGIN: 139664350544872 LOCK_TYPE: RECORD LOCK_MODE: X LOCK_STATUS: GRANTED