Sign inTry Free

Important

New database features are no longer connected to engine versions; features are now enabled independently during scheduled update windows, and “major” and “minor” releases no longer exist in Helios. Please visit the release notes to view the latest features available in your database clusters.

MV_RESOURCE_POOL_STATUS

This view contains information about the status of resource pools aggregating this information across all nodes in the cluster.

The view LMV_RESOURCE_POOL_STATUS provides the same resource pool status information as a local view for a specific node.

Column Name

Description

NODE_ID

The ID of the related node.

POOL_NAME

The name of a given resource pool.

RUNNING_QUERIES

The number of queries running on a given resource pool. This statistic is dependent on the current state of the server.

QUEUEING_QUERIES

The number of queries queued for a given resource pool. This statistic is dependent on the current state of the server.

KILLED_QUERIES

The number of queries killed on a given resource pool. This statistic is cumulative from the start of the server for that node.

FINISHED_QUERIES

The number of queries finished on a given resource pool. This statistic is cumulative from the start of the server for that node.

TOTAL_QUEUE_TIME_US

The historical total queue time for a given resource pool. This statistic is cumulative from the start of the server for that node.

AVERAGE_QUEUE_TIME_US

The historical average queue time for a given resource pool. This statistic is cumulative from the start of the server for that node.

CPU_AFFINITY_MASK

A boolean mask showing which CPU is designated for the queries in a given resource pool.

MEMORY_USAGE_BYTES

The amount of memory (in bytes) currently utilized by the associated resource pool. It is useful for monitoring resource allocation and detecting memory bottlenecks within the resource pools.

Last modified:

Was this article helpful?

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In