Oracle 5.0 Reference Manual page 1690

•
Commit count.
that were committed in the last reporting interval. Because some transactions committed in this
reporting interval may have started in a previous reporting interval, it is possible for
to be greater than
Trans
• This is the number of primary key read operations using this TC as the transaction
Read count.
coordinator that were started in the last reporting interval, including simple reads. This count
also includes reads performed as part of unique index operations. A unique index read operation
generates 2 primary key read operations—1 for the hidden unique index table, and 1 for the table on
which the read takes place.
•
Simple read count.
transaction coordinator that were started in the last reporting interval. This is a subset of
count. Because the value of
from count, it can lag behind
Read
is not equal to
count
time were in fact simple reads.
• This is the number of primary key write operations using this TC as the
Write count.
transaction coordinator that were started in the last reporting interval. This includes all inserts,
updates, writes and deletes, as well as writes performed as part of unique index operations.
Note
A unique index update operation can generate multiple PK read and write
operations on the index table and on the base table.
• AttrInfoCount.
for primary key operations using this TC as the transaction coordinator. For reads, this is proportional
to the number of columns requested. For inserts and updates, this is proportional to the number of
columns written, and the size of their data. For delete operations, this is usually zero. Unique index
operations generate multiple PK operations and so increase this count. However, data words sent
to describe the PK operation itself, and the key information sent, are not counted here. Attribute
information sent to describe columns to read for scans, or to describe ScanFilters, is also not
counted in AttrInfoCount.
•
Concurrent Operations.
TC as the transaction coordinator that were started during the last reporting interval but that were
not completed. Operations increment this counter when they are started and decrement it when
they are completed; this occurs after the transaction commits. Dirty reads and writes—as well as
failed operations—decrement this counter. The maximum value that
can have is the maximum number of operations that a TC block can support; currently, this is
* MaxNoOfConcurrentOperations) + 16 +
more information about these configuration parameters, see the Transaction Parameters section of
Section 17.3.2.5, "Defining MySQL Cluster Data
• This is the number of transactions using this TC as the transaction coordinator
Abort count.
that were aborted during the last reporting interval. Because some transactions that were aborted
in the last reporting interval may have started in a previous reporting interval,
sometimes be greater than
• Scans. This is the number of table scans using this TC as the transaction coordinator that were
started during the last reporting interval. This does not include range scans (that is, ordered index
scans).
• This is the number of ordered index scans using this TC as the transaction
Range scans.
coordinator that were started in the last reporting interval.
Local query handler statistics (Operations).
block (that is, 1 per data node process). Operations are recorded in the LQH where the data they are
operating on resides.
Event Reports Generated in MySQL Cluster
This is the number of transactions using this TC as the transaction coordinator
count.
This is the number of simple read operations using this TC as the
Simple read count
Read count
for a given reporting interval, even if all reads made during that
Read count
This is the number of 32-bit data words received in the last reporting interval
This is the number of primary key or scan operations using this
Trans count.
1670
is incremented at a different point in time
slightly, so it is conceivable that
Concurrent Operations
MaxNoOfConcurrentTransactions. (For
Nodes".)
There is 1 cluster event per local query handler
Commit count
Read
Simple read
(2
can
Abort count