PDF (A4) - 40.9Mb
Man Pages (TGZ) - 261.1Kb
Man Pages (Zip) - 368.3Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb
Thecluster_operations table provides a per-operation (stateful primary key op) view of all activity in the NDB Cluster from the point of view of the local data management (LQH) blocks (seeThe DBLQH Block).
Thecluster_operations table contains the following columns:
node_idNode ID of reporting LQH block
block_instanceLQH block instance
transidTransaction ID
operation_typeOperation type (see text for possible values)
stateOperation state (see text for possible values)
tableidTable ID
fragmentidFragment ID
client_node_idClient node ID
client_block_refClient block reference
tc_node_idTransaction coordinator node ID
tc_block_noTransaction coordinator block number
tc_block_instanceTransaction coordinator block instance
Notes
The transaction ID is a unique 64-bit number which can be obtained using the NDB API'sgetTransactionId() method. (Currently, the MySQL Server does not expose the NDB API transaction ID of an ongoing transaction.)
Theoperation_type column can take any one of the valuesREAD,READ-SH,READ-EX,INSERT,UPDATE,DELETE,WRITE,UNLOCK,REFRESH,SCAN,SCAN-SH,SCAN-EX, or<unknown>.
Thestate column can have any one of the valuesABORT_QUEUED,ABORT_STOPPED,COMMITTED,COMMIT_QUEUED,COMMIT_STOPPED,COPY_CLOSE_STOPPED,COPY_FIRST_STOPPED,COPY_STOPPED,COPY_TUPKEY,IDLE,LOG_ABORT_QUEUED,LOG_COMMIT_QUEUED,LOG_COMMIT_QUEUED_WAIT_SIGNAL,LOG_COMMIT_WRITTEN,LOG_COMMIT_WRITTEN_WAIT_SIGNAL,LOG_QUEUED,PREPARED,PREPARED_RECEIVED_COMMIT,SCAN_CHECK_STOPPED,SCAN_CLOSE_STOPPED,SCAN_FIRST_STOPPED,SCAN_RELEASE_STOPPED,SCAN_STATE_USED,SCAN_STOPPED,SCAN_TUPKEY,STOPPED,TC_NOT_CONNECTED,WAIT_ACC,WAIT_ACC_ABORT,WAIT_AI_AFTER_ABORT,WAIT_ATTR,WAIT_SCAN_AI,WAIT_TUP,WAIT_TUPKEYINFO,WAIT_TUP_COMMIT, orWAIT_TUP_TO_ABORT. (If the MySQL Server is running withndbinfo_show_hidden enabled, you can view this list of states by selecting from thendb$dblqh_tcconnect_state table, which is normally hidden.)
You can obtain the name of anNDB table from its table ID by checking the output ofndb_show_tables.
Thefragid is the same as the partition number seen in the output ofndb_desc--extra-partition-info (short form-p).
Inclient_node_id andclient_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).
Theblock_instance andtc_block_instance column provide, respectively, theDBLQH andDBTC block instance numbers. You can use these along with the block names to obtain information about specific threads from thethreadblocks table.
PDF (A4) - 40.9Mb
Man Pages (TGZ) - 261.1Kb
Man Pages (Zip) - 368.3Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb