This table provides information about data node resource availability and usage.
These resources are sometimes known as super-pools.
The following table provides information about the columns in
resources 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
|integer||The unique node ID of this data node.|
|string||Name of the resource; see text.|
|integer||The amount reserved for this resource.|
|integer||The amount actually used by this resource.|
|integer||The maximum amount of this resource used, since the node was last started.|
resource_name can be one of the names
shown in the following table:
|Reserved by the system; cannot be overridden.|
|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
|Records allocated for Disk Data operations.|
|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.|
|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.|
|Used by the redo log handler in the |
|Used for send buffers by ndbmtd; the sum of
|Used for the disk page buffer; determined by the
|Used by the |
|Minimum is 2 MB; can be overallocated to use any remaining available memory.|