No cache version.
Caching disabled. Default setting for this page:enabled (code DEF204)If the display is too slow, you can disable the user mode to view the cached version.
Rechercher dans le manuel MySQL
22.5.10.6 The ndbinfo cluster_transactions Table
The cluster_transactions table shows
information about all ongoing transactions in an NDB 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.
Table 22.380 Columns of the cluster_transactions table
| Column Name | Type | Description |
|---|---|---|
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 reads with 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()
method. (Currently, the MySQL Server does not expose the NDB API
transaction ID of an ongoing transaction.)
block_instance refers to an instance of a
kernel block. Together with the block name, this number can be
used to look up a given instance in the
threadblocks table.
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 an NDB Cluster API or SQL node (that is, an NDB API
client or a MySQL Server attached to the cluster).
The tc_block_instance column provides the
DBTC block instance number. You can use this
along with the block name to obtain information about specific
threads from the threadblocks
table.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-mysql-cluster-ndbinfo-cluster-transactions.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.
