RESOURCE_POOL_STATUS

Provides configuration settings of the various resource pools in the system, including internal pools. For detailed information about resource parameters, see CREATE RESOURCE POOL or ALTER RESOURCE POOL.

Column Name Data Type Description
NODE_NAME VARCHAR

The name of the node for which information is provided.
POOL_OID INTEGER

A unique numeric ID that identifies the pool and is assigned by the Vertica catalog.

POOL_NAME VARCHAR

The name of the resource pool.
IS_INTERNAL BOOLEAN

Denotes whether a pool is one of the Built-In Pools.

MEMORY_SIZE_KB INTEGER

Value of MEMORYSIZE setting of the pool in kilobytes.
MEMORY_SIZE_ACTUAL_KB INTEGER

Current amount of memory, in kilobytes, allocated to the pool by the resource manager. The actual size can be less than specified in the DDL, if both the following conditions exist:

  • The pool has been recently altered in a running system.
  • The request to shuffle memory is pending.
MEMORY_INUSE_KB INTEGER

Amount of memory, in kilobytes, acquired by requests running against this pool.
GENERAL_MEMORY_BORROWED_KB INTEGER

Amount of memory, in kilobytes, borrowed from the GENERAL pool by requests running against this pool. The sum of MEMORY_INUSE_KB and GENERAL_MEMORY_BORROWED_KB should be less than MAX_MEMORY_SIZE_KB.
QUEUEING_THRESHOLD_KB INTEGER

Calculated as MAX_MEMORY_SIZE_KB * 0.95. When the amount of memory used by all requests against this resource pool exceeds the QUEUEING_THRESHOLD_KB, new requests against the pool are queued until memory becomes available.

MAX_MEMORY_SIZE_KB INTEGER

Value, in kilobytes, of the MAXMEMORYSIZE parameter specified when defining the pool. After this threshold is reached, new requests against this pool are rejected or queued until memory becomes available.

MAX_MEMORY_SIZE_KB might not reflect the set MAXMEMORYSIZE parameter value if the specified value cannot be reached.

Example:

If MAXMEMORYSIZE = 10G, but less than 2G is available, MAX_MEMORY_SIZE_KB will not reflect the original value in KB, but will instead reflect 2G in KB, since that is the highest value that can be reached.

Ordinarily, the ALTER RESOURCE POOL and CREATE RESOURCE POOL statements provide error messages to prevent setting the MAXMEMORYSIZE to a value greater than available, but making system changes or other configuration changes can cause this scenario.
RUNNING_QUERY_COUNT INTEGER

Number of queries actually running using this pool.

PLANNED_CONCURRENCY INTEGER

Value of PLANNEDCONCURRENCY parameter specified when defining the pool.

MAX_CONCURRENCY INTEGER

Value of MAXCONCURRENCY parameter specified when defining the pool.
IS_STANDALONE BOOLEAN

If the pool is configured to have MEMORYSIZE equal to MAXMEMORYSIZE, the pool is considered standalone because it does not borrow any memory from the General pool.

QUEUE_TIMEOUT INTERVAL The interval that the request waits for resources to become available before being rejected. If you set this value to NONE, Vertica displays it as NULL.
QUEUE_TIMEOUT_IN_SECONDS INTEGER

Value of QUEUETIMEOUT parameter that was specified when defining the pool. If you set QUEUE_TIMEOUT to NONE, Vertica displays this value as NULL.
EXECUTION_PARALLELISM INTEGER

Limits the number of threads used to process any single query issued in this resource pool.
PRIORITY INTEGER

Value of PRIORITY parameter specified when defining the pool.

When set to HOLD, Vertica sets a pool's priority to -999 so the query remains queued until QUEUETIMEOUT is reached.

RUNTIME_PRIORITY VARCHAR

Value of RUNTIME_PRIORITY specified when defining the pool.
RUNTIME_PRIORITY_THRESHOLD INTEGER

Value of RUNTIME_PRIORITY_THRESHOLD specified when defining the pool.
SINGLE_INITIATOR

BOOLEAN

Value of SINGLEINITIATOR parameter specified when defining the pool.
QUERY_BUDGET_KB INTEGER

The current amount of memory that queries are tuned to use. The calculation that Vertica uses to determine this value is described inTarget Memory Determination for Queries in Concurrent Environments.

Note: The calculated value can change when one or more running queries needs more than the budgeted amount to run.

For a detailed example of query budget calculations, see Do You Need to Put Your Query on a Budget? in the Vertica User Community.
CPU_AFFINITY_SET VARCHAR

The set of CPUs on which queries associated with this pool are executed. Can be:

  • A percentage of CPUs on the system
  • A zero-based list of CPUs (a four-CPU system c of CPUs 0, 1, 2, and 3).
CPU_AFFINITY_MASK VARCHAR

The bit mask of CPUs available for use in this pool.

Valid values: Hex-encoded binaries for the CPUs on the system. Read from right to left.

Example:

A pool that has exclusive use of CPUs 0 and 1 on a four-CPU system is represented by the hex value of 3, which translates to 0011. The 1's indicates the that CPU 0 and 1 are available.

If no other resource pools use exclusive CPU affinities, the remaining resource pools in this example have a mask of 3, which translates to 1100. Thus, CPUs 2 and 3 of the four CPUs on the system are available to these resource pools.
CPU_AFFINITY_MODE VARCHAR

The mode for the CPU affinity, one of the following:

  • ANY
  • EXCLUSIVE
  • SHARED

See Also