ndbinfo: The NDB Cluster Information Database The  fragid  is the same as the partition number seen in the output of  ndb_desc --extra-partition- info  (short form  -p ). In  client_node_id  and  client_block_ref ,  client  refers to an NDB Cluster API or SQL node (that is, an NDB API client or a MySQL Server attached to the cluster). The  block_instance  and  tc_block_instance  column provide, respectively, the  DBLQH  and  DBTC block instance numbers. You can use these along with the block names to obtain information about specific threads from the  threadblocks  table. The  cluster_transactions  table shows information about all ongoing transactions in an NDB Cluster. The  cluster_transactions  table contains the following columns: Node ID of transaction coordinator TC block instance Transaction ID Operation state (see text for possible values) Number of stateful primary key operations in transaction (includes reads with locks, as well as DML operations) Operations still being executed in local data management blocks Time spent waiting for API Client node ID Client block reference The transaction ID is a unique 64-bit number which can be obtained using the NDB API’s getTransactionId()  method. (Currently, the MySQL Server does not expose the NDB API transaction ID of an ongoing transaction.) 4530 Notes 23.5.14.7 The ndbinfo cluster_transactions Table • node_id • block_instance • transid • state • count_operations • outstanding_operations • inactive_seconds • client_node_id • client_block_ref