MV_ ACTIVITIES_ CUMULATIVE
This view provides a high-level summary profile of completed and currently running tasks on all nodes of the cluster.
It holds a row per high-level activity H.
The effect of grouping the instances of multiple activities together is mainly to group all tasks associated with a query, across all partitions, into a single row.
For cross-database queries, activities in this table are tracked in relation to the context database of the local query.
mv_
may only be queried while connected to an aggregator node.
SingleStore recommends against extensive use of this table.
Column name |
Description |
---|---|
|
The |
|
An ID shared by all instances of the high level activity. |
|
The name of the database associated with the activity, or |
|
The timestamp of the most recent completion of an instance of this activity. |
|
The number of running instances of the activity. |
|
The number of successfully completed instances of the activity. |
|
The number of unsuccessfully completed instances of the activity. |
This view contains all simplified statistics columns, including: |
|
|
A query sometimes cannot find its input data in blob cache, referred to as a cache miss. |
|
The time (milliseconds) that were spent on waiting for blob cache data. |
Last modified: October 17, 2024