The server_operations NDB, SQL . It effectively is a subset of the NDB cluster_operations, SQL API 。

The server_operations :

The mysql_connection_id SHOW PROCESSLIST . It is obtained from the INFORMATION_SCHEMA table NDB_TRANSID_MYSQL_CONNECTION_MAP.

block_instance . Together with the block name, this number can be used to look up a given instance in the threadblocks table.

The transaction ID (transid) 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.)

The operation_type column can take any one of the values READ, READ-SH, READ-EX, INSERT, UPDATE, DELETE, WRITE, UNLOCK, REFRESH, SCAN, SCAN-SH, SCAN-EX, or <unknown>.

该 state 列可以具有以下任何一个值：ABORT_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 或 WAIT_TUP_TO_ABORT。(如果 MySQL 服务器正在运行 ndbinfo_show_hidden 启用，可以通过从 ndb$dblqh_tcconnect_state 表中选择来查看这些状态列表，该表通常是隐藏的。)

您可以通过检查 ndb_show_tables 的输出来从表 ID 获取 NDB 表的名称。

该 fragid 与 ndb_desc --extra-partition-info (短形式 -p) 输出中的分区号相同。

在 client_node_id 和 client_block_ref 中，client 指的是 NDB 集群 API 或 SQL 节点（即 NDB API 客户端或附加到集群的 MySQL 服务器）。

该 block_instance 和 tc_block_instance 列提供 NDB 内核块实例编号。您可以使用这些编号从 threadblocks 表中获取特定线程的信息。