<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h4 class="title">
      <a name="mysql-cluster-ndbinfo-cluster-operations">
      </a>
      25.6.17.8 The ndbinfo cluster_operations Table
     </h4>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045090365744">
  </a>
  <p>
   The
   <code class="literal">
    cluster_operations
   </code>
   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
   <a class="ulink" href="/doc/ndb-internals/en/ndb-internals-kernel-blocks-dblqh.html" target="_top">
    The DBLQH Block
   </a>
   ).
  </p>
  <p>
   The
   <code class="literal">
    cluster_operations
   </code>
   table contains the
        following columns:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <code class="literal">
       node_id
      </code>
     </p>
     <p>
      Node ID of reporting LQH block
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       block_instance
      </code>
     </p>
     <p>
      LQH block instance
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       transid
      </code>
     </p>
     <p>
      Transaction ID
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       operation_type
      </code>
     </p>
     <p>
      Operation type (see text for possible values)
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       state
      </code>
     </p>
     <p>
      Operation state (see text for possible values)
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       tableid
      </code>
     </p>
     <p>
      Table ID
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       fragmentid
      </code>
     </p>
     <p>
      Fragment ID
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       client_node_id
      </code>
     </p>
     <p>
      Client node ID
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       client_block_ref
      </code>
     </p>
     <p>
      Client block reference
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       tc_node_id
      </code>
     </p>
     <p>
      Transaction coordinator node ID
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       tc_block_no
      </code>
     </p>
     <p>
      Transaction coordinator block number
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       tc_block_instance
      </code>
     </p>
     <p>
      Transaction coordinator block instance
     </p>
    </li>
   </ul>
  </div>
  <h5>
   <a name="idm46045090337808">
   </a>
   Notes
  </h5>
  <p>
   The transaction ID is a unique 64-bit number which can be
        obtained using the NDB API's
   <a class="ulink" href="/doc/ndbapi/en/ndb-ndbtransaction.html#ndb-ndbtransaction-gettransactionid" target="_top">
    <code class="literal">
     getTransactionId()
    </code>
   </a>
   method. (Currently, the MySQL Server does not expose the NDB API
        transaction ID of an ongoing transaction.)
  </p>
  <p>
   The
   <code class="literal">
    operation_type
   </code>
   column can take any one of
        the values
   <code class="literal">
    READ
   </code>
   ,
   <code class="literal">
    READ-SH
   </code>
   ,
   <code class="literal">
    READ-EX
   </code>
   ,
   <code class="literal">
    INSERT
   </code>
   ,
   <code class="literal">
    UPDATE
   </code>
   ,
   <code class="literal">
    DELETE
   </code>
   ,
   <code class="literal">
    WRITE
   </code>
   ,
   <code class="literal">
    UNLOCK
   </code>
   ,
   <code class="literal">
    REFRESH
   </code>
   ,
   <code class="literal">
    SCAN
   </code>
   ,
   <code class="literal">
    SCAN-SH
   </code>
   ,
   <code class="literal">
    SCAN-EX
   </code>
   , or
   <code class="literal">
    &lt;unknown&gt;
   </code>
   .
  </p>
  <p>
   The
   <code class="literal">
    state
   </code>
   column can have any one of the
        values
   <code class="literal">
    ABORT_QUEUED
   </code>
   ,
   <code class="literal">
    ABORT_STOPPED
   </code>
   ,
   <code class="literal">
    COMMITTED
   </code>
   ,
   <code class="literal">
    COMMIT_QUEUED
   </code>
   ,
   <code class="literal">
    COMMIT_STOPPED
   </code>
   ,
   <code class="literal">
    COPY_CLOSE_STOPPED
   </code>
   ,
   <code class="literal">
    COPY_FIRST_STOPPED
   </code>
   ,
   <code class="literal">
    COPY_STOPPED
   </code>
   ,
   <code class="literal">
    COPY_TUPKEY
   </code>
   ,
   <code class="literal">
    IDLE
   </code>
   ,
   <code class="literal">
    LOG_ABORT_QUEUED
   </code>
   ,
   <code class="literal">
    LOG_COMMIT_QUEUED
   </code>
   ,
   <code class="literal">
    LOG_COMMIT_QUEUED_WAIT_SIGNAL
   </code>
   ,
   <code class="literal">
    LOG_COMMIT_WRITTEN
   </code>
   ,
   <code class="literal">
    LOG_COMMIT_WRITTEN_WAIT_SIGNAL
   </code>
   ,
   <code class="literal">
    LOG_QUEUED
   </code>
   ,
   <code class="literal">
    PREPARED
   </code>
   ,
   <code class="literal">
    PREPARED_RECEIVED_COMMIT
   </code>
   ,
   <code class="literal">
    SCAN_CHECK_STOPPED
   </code>
   ,
   <code class="literal">
    SCAN_CLOSE_STOPPED
   </code>
   ,
   <code class="literal">
    SCAN_FIRST_STOPPED
   </code>
   ,
   <code class="literal">
    SCAN_RELEASE_STOPPED
   </code>
   ,
   <code class="literal">
    SCAN_STATE_USED
   </code>
   ,
   <code class="literal">
    SCAN_STOPPED
   </code>
   ,
   <code class="literal">
    SCAN_TUPKEY
   </code>
   ,
   <code class="literal">
    STOPPED
   </code>
   ,
   <code class="literal">
    TC_NOT_CONNECTED
   </code>
   ,
   <code class="literal">
    WAIT_ACC
   </code>
   ,
   <code class="literal">
    WAIT_ACC_ABORT
   </code>
   ,
   <code class="literal">
    WAIT_AI_AFTER_ABORT
   </code>
   ,
   <code class="literal">
    WAIT_ATTR
   </code>
   ,
   <code class="literal">
    WAIT_SCAN_AI
   </code>
   ,
   <code class="literal">
    WAIT_TUP
   </code>
   ,
   <code class="literal">
    WAIT_TUPKEYINFO
   </code>
   ,
   <code class="literal">
    WAIT_TUP_COMMIT
   </code>
   , or
   <code class="literal">
    WAIT_TUP_TO_ABORT
   </code>
   . (If the MySQL Server is
        running with
   <a class="link" href="mysql-cluster-options-variables.html#sysvar_ndbinfo_show_hidden">
    <code class="literal">
     ndbinfo_show_hidden
    </code>
   </a>
   enabled,
        you can view this list of states by selecting from the
   <code class="literal">
    ndb$dblqh_tcconnect_state
   </code>
   table, which is
        normally hidden.)
  </p>
  <p>
   You can obtain the name of an
   <code class="literal">
    NDB
   </code>
   table from
        its table ID by checking the output of
   <a class="link" href="mysql-cluster-programs-ndb-show-tables.html" title="25.5.27 ndb_show_tables — Display List of NDB Tables">
    <span class="command">
     <strong>
      ndb_show_tables
     </strong>
    </span>
   </a>
   .
  </p>
  <p>
   The
   <code class="literal">
    fragid
   </code>
   is the same as the partition
        number seen in the output of
   <a class="link" href="mysql-cluster-programs-ndb-desc.html" title="25.5.9 ndb_desc — Describe NDB Tables">
    <span class="command">
     <strong>
      ndb_desc
     </strong>
    </span>
   </a>
   <a class="link" href="mysql-cluster-programs-ndb-desc.html#option_ndb_desc_extra-partition-info">
    <code class="option">
     --extra-partition-info
    </code>
   </a>
   (short
        form
   <code class="option">
    -p
   </code>
   ).
  </p>
  <p>
   In
   <code class="literal">
    client_node_id
   </code>
   and
   <code class="literal">
    client_block_ref
   </code>
   ,
   <code class="literal">
    client
   </code>
   refers to an NDB Cluster API or SQL node (that is, an NDB API
        client or a MySQL Server attached to the cluster).
  </p>
  <p>
   The
   <code class="literal">
    block_instance
   </code>
   and
   <code class="literal">
    tc_block_instance
   </code>
   column provide,
        respectively, the
   <a class="ulink" href="/doc/ndb-internals/en/ndb-internals-kernel-blocks-dblqh.html" target="_top">
    <code class="literal">
     DBLQH
    </code>
   </a>
   and
   <a class="ulink" href="/doc/ndb-internals/en/ndb-internals-kernel-blocks-dbtc.html" target="_top">
    <code class="literal">
     DBTC
    </code>
   </a>
   block instance numbers.
        You can use these along with the block names to obtain
        information about specific threads from the
   <a class="link" href="mysql-cluster-ndbinfo-threadblocks.html" title="25.6.17.62 The ndbinfo threadblocks Table">
    <code class="literal">
     threadblocks
    </code>
   </a>
   table.
  </p>
 </div>
 <br/>
</div>
