Rechercher dans le manuel MySQL
22.5.10.34 The ndbinfo server_operations Table
The server_operations table contains entries
for all ongoing NDB operations that
the current SQL node (MySQL Server) is currently involved in. It
effectively is a subset of the
cluster_operations table, in
which operations for other SQL and API nodes are not shown.
The following table provides information about the columns in
the server_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.410 Columns of the server_operations table
| Column Name | Type | Description |
|---|---|---|
mysql_connection_id |
integer | MySQL Server connection ID |
node_id |
integer | Node ID |
block_instance |
integer | 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 mysql_connection_id is the same as the
connection or session ID shown in the output of
SHOW PROCESSLIST. It is obtained
from the INFORMATION_SCHEMA table
NDB_TRANSID_MYSQL_CONNECTION_MAP.
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 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>.
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 NDB kernel
block instance numbers. You can use these to obtain information
about specific threads from the
threadblocks table.
Traduction non disponible
Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.
Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-mysql-cluster-ndbinfo-server-operations.html
L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.
Références
Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.
