Rechercher dans le manuel MySQL
22.5.10.5 The ndbinfo cluster_operations Table
The cluster_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 (see
The DBLQH Block).
The following table provides information about the columns in
the cluster_operations
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.379 Columns of the cluster_operations table
Column Name | Type | Description |
---|---|---|
node_id |
integer | Node ID of reporting LQH block |
block_instance |
integer | LQH block instance |
transid |
integer | Transaction ID |
operation_type |
string | Operation type (see text for possible values) |
state |
string | Operation state (see text for possible values) |
tableid |
integer | Table ID |
fragmentid |
integer | Fragment ID |
client_node_id |
integer | Client node ID |
client_block_ref |
integer | Client block reference |
tc_node_id |
integer | Transaction coordinator node ID |
tc_block_no |
integer | Transaction coordinator block number |
tc_block_instance |
integer | Transaction coordinator block instance |
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.)
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>
.
The state
column can have any one of the
values 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
, or
WAIT_TUP_TO_ABORT
. (If the MySQL Server is
running with
ndbinfo_show_hidden
enabled,
you can view this list of states by selecting from the
ndb$dblqh_tcconnect_state
table, which is
normally hidden.)
You can obtain the name of an NDB
table from
its table ID by checking the output of
ndb_show_tables.
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.
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-operations.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.