Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

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.
`activity_tracking_id`	An ID that can be used to identify the activities associated with a session. Configure the `activity_tracking_id` session engine variable to specify an ID for all the activities associated with the queries run in the current session. In the case of pipeline queries, this value is set automatically in the following way: If the queries are directly run by the pipeline, their `activity_tracking_id` is `PI_<PIPELINE_ID>`. If the pipeline calls a stored procedure, the `activity_tracking_id` of the queries run by this stored procedure is set as `PR_PI_<PIPELINE_ID>`.
`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`.
`BLOB_CACHE_MISS_B`	A query sometimes cannot find its input data in blob cache, referred to as a cache miss. The blob cache will download the missing data from the unlimited storage. This new field tells us the number of bytes downloaded from the unlimited storage.
`BLOB_CACHE_WAIT_TIME_MS`	The time (milliseconds) that were spent on waiting for blob cache data. This is a sum of waiting time from all query execution threads, not to be compared with end-to-end running time.

MV_TASKS

Was this article helpful?

Was this article helpful?