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. 

## 23.5.14.7 The ndbinfo cluster_transactions 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 

Node ID of transaction coordinator 

• block_instance 

TC block instance 

• transid 

Transaction ID 

• state 

Operation state (see text for possible values) 

• count_operations 

Number of stateful primary key operations in transaction (includes reads with locks, as well as DML operations) 

## Notes 

• outstanding_operations 

Operations still being executed in local data management blocks 

• inactive_seconds 

Time spent waiting for API 

• client_node_id 

Client node ID 

• client_block_ref 

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.) 

