Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 9.1.

MV_PROCESSLIST

This view contains information about currently running threads on a cluster for all nodes. Alternatively, information_schema.PROCESSLIST shows this information per node. This information is surfaced by the SHOW PROCESSLIST command.

Column Name

Description

NODE_ID

The ID of the node a given process is being run on.

ID

The unique ID of a given process.

USER

The user who issued the process command.

HOST

The hostname or IP address from which the connection originated.

DB

The related database.

COMMAND

The type of command associated with this process.

TIME

The runtime, in seconds.

STATE

The state of a given process.

INFO

Additional information about a given process, including the query text.

FUNCTION_NAME

The name of the calling Stored Procedure, if the process was called by a Stored Procedure.

RPC_INFO

Low level information about this process shown as a JSON string.

PLAN_ID

The ID of the related query plan for a given process.

TRANSACTION_STATE

running if there is an open transaction and a query running. open if there is an open transaction with no query running. NULL if there is no open transaction.

ROW_LOCKS_HELD

The number of row locks being held.

PARTITION_LOCKS_HELD

The column is deprecated, as are partition level locks. The value for this column is always 0.

LWPID

The native OS thread ID (lightweight process ID).

RESOURCE_POOL

The resource pool a given process is drawing from.

DRAINING

Specifies if the current connection is draining.

REASON_FOR_QUEUEING

The reason a given process is queued.

DAC_CONNECTION

Specifies if the current connection is a Dedicated Admin Connection (DAC).

IP_ADDRESS

IP address of the connection.

Last modified: February 27, 2026

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