<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h4 class="title">
      <a name="mysql-cluster-ndbinfo-resources">
      </a>
      25.6.17.52 The ndbinfo resources Table
     </h4>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045088199376">
  </a>
  <p>
   This table provides information about data node resource
        availability and usage.
  </p>
  <p>
   These resources are sometimes known as
   <span class="firstterm">
    super-pools
   </span>
   .
  </p>
  <p>
   The
   <code class="literal">
    resources
   </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>
      The unique node ID of this data node.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       resource_name
      </code>
     </p>
     <p>
      Name of the resource; see text.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       reserved
      </code>
     </p>
     <p>
      The amount reserved for this resource, as a number of 32KB
            pages.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       used
      </code>
     </p>
     <p>
      The amount actually used by this resource, as a number of
            32KB pages.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       max
      </code>
     </p>
     <p>
      The maximum amount (number of 32KB pages) of this resource
            that is available to this data node.
     </p>
    </li>
   </ul>
  </div>
  <h5>
   <a name="idm46045088184944">
   </a>
   Notes
  </h5>
  <p>
   The
   <code class="literal">
    resource_name
   </code>
   can be any one of the names
        shown in the following table:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <code class="literal">
       RESERVED
      </code>
      : Reserved by the system; cannot
            be overridden.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       TRANSACTION_MEMORY
      </code>
      : Memory allocated for
            transactions on this data node. This can be controlled using
            the
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-transactionmemory">
       <code class="literal">
        TransactionMemory
       </code>
      </a>
      configuration parameter.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       DISK_OPERATIONS
      </code>
      : If a log file group is
            allocated, the size of the undo log buffer is used to set
            the size of this resource. This resource is used only to
            allocate the undo log buffer for an undo log file group;
            there can only be one such group. Overallocation occurs as
            needed by
      <a class="link" href="create-logfile-group.html" title="15.1.16 CREATE LOGFILE GROUP Statement">
       <code class="literal">
        CREATE LOGFILE
            GROUP
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       DISK_RECORDS
      </code>
      : Records allocated for Disk
            Data operations.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       DATA_MEMORY
      </code>
      : Used for main memory tuples,
            indexes, and hash indexes. Sum of DataMemory and
            IndexMemory, plus 8 pages of 32 KB each if IndexMemory has
            been set. Cannot be overallocated.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       JOBBUFFER
      </code>
      : Used for allocating job
            buffers by the NDB scheduler; cannot be overallocated. This
            is approximately 2 MB per thread plus a 1 MB buffer in both
            directions for all threads that can communicate. For large
            configurations this consume several GB.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       FILE_BUFFERS
      </code>
      : Used by the redo log
            handler in the
      <a class="ulink" href="/doc/ndb-internals/en/ndb-internals-kernel-blocks-dblqh.html" target="_top">
       <code class="literal">
        DBLQH
       </code>
      </a>
      kernel block; cannot be overallocated. Size is
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbmtd-nooffragmentlogparts">
       <code class="literal">
        NoOfFragmentLogParts
       </code>
      </a>
      *
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-redobuffer">
       <code class="literal">
        RedoBuffer
       </code>
      </a>
      , plus 1
            MB per log file part.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       TRANSPORTER_BUFFERS
      </code>
      : Used for send
            buffers by
      <a class="link" href="mysql-cluster-programs-ndbmtd.html" title="25.5.3 ndbmtd — The NDB Cluster Data Node Daemon (Multi-Threaded)">
       <span class="command">
        <strong>
         ndbmtd
        </strong>
       </span>
      </a>
      ; the sum of
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-totalsendbuffermemory">
       <code class="literal">
        TotalSendBufferMemory
       </code>
      </a>
      and
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-extrasendbuffermemory">
       <code class="literal">
        ExtraSendBufferMemory
       </code>
      </a>
      .
            This resource that can be overallocated by up to 25 percent.
      <code class="literal">
       TotalSendBufferMemory
      </code>
      is calculated by
            summing the send buffer memory per node, the default value
            of which is 2 MB. Thus, in a system having four data nodes
            and eight API nodes, the data nodes have 12 * 2 MB send
            buffer memory.
      <code class="literal">
       ExtraSendBufferMemory
      </code>
      is
            used by
      <a class="link" href="mysql-cluster-programs-ndbmtd.html" title="25.5.3 ndbmtd — The NDB Cluster Data Node Daemon (Multi-Threaded)">
       <span class="command">
        <strong>
         ndbmtd
        </strong>
       </span>
      </a>
      and amounts to 2 MB extra
            memory per thread. Thus, with 4 LDM threads, 2 TC threads, 1
            main thread, 1 replication thread, and 2 receive threads,
      <code class="literal">
       ExtraSendBufferMemory
      </code>
      is 10 * 2 MB.
            Overallocation of this resource can be performed by setting
            the
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-sharedglobalmemory">
       <code class="literal">
        SharedGlobalMemory
       </code>
      </a>
      data node configuration parameter.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       DISK_PAGE_BUFFER
      </code>
      : Used for the disk page
            buffer; determined by the
      <a class="link" href="mysql-cluster-ndbd-definition.html#ndbparam-ndbd-diskpagebuffermemory">
       <code class="literal">
        DiskPageBufferMemory
       </code>
      </a>
      configuration parameter. Cannot be overallocated.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       QUERY_MEMORY
      </code>
      : Used by the
      <a class="ulink" href="/doc/ndb-internals/en/ndb-internals-kernel-blocks-dbspj.html" target="_top">
       <code class="literal">
        DBSPJ
       </code>
      </a>
      kernel block.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       SCHEMA_TRANS_MEMORY
      </code>
      : Minimum is 2 MB; can
            be overallocated to use any remaining available memory.
     </p>
    </li>
   </ul>
  </div>
 </div>
 <br/>
</div>
