Sign inTry Free

MV_TASKS

This view provides a detailed profile of all currently running tasks on all nodes of the cluster.

It holds a row per running task. Each row reports the profiling statistics of the task, as collected between the time it began and the current time.

mv_tasks may only be queried while connected to an aggregator node.

SingleStore recommends against extensive use of this view. It will hide the performance impact of short-lived but frequent tasks, and exaggerate the impact of long-lived tasks.

Column name

Description

node_id

An ID equal to id in the row of mv_nodes describing the node on which the task is running.

activity_type

The type of the task’s activity.

activity_name

An ID shared by all instances of the task’s activity. This ID is often human-readable, but does not include the query text for query tasks.

aggregator_activity_name

The aggregator_activity_name of the task’s activity.

database_name

The name of the database associated with the task’s activity, or NULL if none could be assigned.

partition_id

The unique ID of the database partition associated with the task’s activity, or NULL if none could be assigned.

raw_task_name

The full name associated with the task, or NULL if none could be assigned. In particular, this will hold the raw query text for query tasks. It differs from query_text in mv_nodes because it is fully parameterized. Note that this column is only available in mv_tasks.

EXTENDED STATISTICS

This view contains all extended statistics columns, including: cpu_time_ms, cpu_wait_time_ms, disk_logical_read_b, disk_logical_write_b, disk_physical_read_b, disk_physical_write_b, disk_time_ms, elapsed_time_ms, lock_row_time_ms, lock_time_ms, log_buffer_b, log_buffer_time_ms, log_flush_time_ms, memory_bs, memory_major_faults, network_logical_recv_b, network_logical_send_b, and network_time_ms.

Last modified: August 18, 2025

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