Spec-Zone .ru
спецификации, руководства, описания, API
|
The cluster_transactions
table shows information about all ongoing transactions in
a MySQL Cluster.
The following table provides information about the columns in the cluster_transactions
table. For each column, the table shows the name, data type, and
a brief description. Additional information can be found in the notes following the table.
Column Name | Type | Remarks |
---|---|---|
node_id |
integer | Node ID of transaction coordinator |
block_instance |
integer | TC block instance |
transid |
integer | Transaction ID |
state |
string | Operation state (see text for possible values) |
count_operations |
integer | Number of stateful primary key operations in transaction (includes readswith locks, as well as DML operations) |
outstanding_operations |
integer | Operations still being executed in local data management blocks |
inactive_seconds |
integer | Time spent waiting for API |
client_node_id |
integer | Client node ID |
client_block_ref |
integer | Client block reference |
The transaction ID is a unique 64-bit number which can be obtained using the NDB API's getTransactionId()
The state
column can have any one of the values CS_ABORTING
, CS_COMMITTING
, CS_COMMIT_SENT
,
CS_COMPLETE_SENT
, CS_COMPLETING
, CS_CONNECTED
, CS_DISCONNECTED
, CS_FAIL_ABORTED
, CS_FAIL_ABORTING
, CS_FAIL_COMMITTED
, CS_FAIL_COMMITTING
, CS_FAIL_COMPLETED
, CS_FAIL_PREPARED
, CS_PREPARE_TO_COMMIT
, CS_RECEIVING
, CS_REC_COMMITTING
, CS_RESTART
, CS_SEND_FIRE_TRIG_REQ
, CS_STARTED
, CS_START_COMMITTING
, CS_START_SCAN
, CS_WAIT_ABORT_CONF
, CS_WAIT_COMMIT_CONF
, CS_WAIT_COMPLETE_CONF
, CS_WAIT_FIRE_TRIG_REQ
. (If
the MySQL Server is running with ndbinfo_show_hidden
enabled, you can view this list of states by selecting
from the ndb$dbtc_apiconnect_state
table, which is normally hidden.)
In client_node_id
and client_block_ref
, client
refers to a MySQL Cluster API or SQL node (that is, an NDB API client or a
MySQL Server attached to the cluster).