Sign inTry Free

Important

Self-managed SingleStore will soon transition from version 9.1 RC to version 10. This new semantic versioning scheme will provide SingleStore with finer control over engine and feature releases that were not possible with the current versioning scheme.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10 prior to its general availability. Ahead of this transition, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 10.

WORKLOAD_MANAGEMENT_QUEUE

This system table shows the current list of queries for which the Workload Management system cannot reserve resources for an execution and therefore has put them into the waiting queue.

It provides a detailed explanation of which resource is lacking (required > (limit - used)), and therefore why the query is queued.

Column Name

Descriptiom

QUERY

Text of query

START_TIME

The  time when the query was submitted for execution

THREADS_PER_LEAF

How many system threads are required for the query execution

THREADS_PER_LEAF_LIMIT

Total number of threads allowed at the time of query submission

THREADS_PER_LEAF_USED

Total number of used threads at the time of query submission

CONNECTIONS_PER_LEAF

How many system connections are required for the query execution

CONNECTIONS_PER_LEAF_LIMIT

Total number of connections allowed at the time of query submission

CONNECTIONS_PER_LEAF_USED

Total number of used connections at the time of query submission

LEAF_MEMORY

How much memory (in MB) is required for the query execution

LEAF_MEMORY_LIMIT

Total amount of memory allowed at the time of query submission

LEAF_MEMORY_USED

Total amount of used memory at the time of query submission

QUERY_TYPE

Medium,  Large (Small queries are never queued)

MEMORY_TYPE

Small, Medium, Large

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