Sign inTry Free

MV_ACTIVITIES_EXTENDED_CUMULATIVE

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

It holds a row per activity. Each row describes completed and currently running instances of its activity. It reports the sum of the profiling statistics of each instance, as collected over its lifetime. Activities can include tasks such as garbage collection and backups, in addition to queries.

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

Be aware when using this view that it does not fully describe past system behavior because it does not include all completed instances. This is because historical task statistics may be discarded by SingleStore at unspecified times.

Column name

Description

node_id

An ID equal to id in the row of mv_nodes describing the node on which the activity’s instances have run.

activity_type

The type of the activity.

activity_name

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

aggregator_activity_name

The aggregator_activity_name of the activity.

database_name

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

partition_id

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

last_finished_timestamp

The timestamp of the most recent completion of an instance of this activity.

run_count

The number of running instances of this activity.

success_count

The number of successfully completed instances of this activity.

failure_count

The number of unsuccessfully completed instances of this activity.

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: October 18, 2024

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