Sign inTry Free

MV_CROSS_QUERY_STATS_CACHE

This view is a managed view that aggregates cross-query stats cache entries across all aggregators in the cluster. Use this view to get a cluster‑wide picture of cache utilization and distribution.

Column Name

Description

HASH

64‑bit hash of the query or subquery shape used as the cache key; matches the fr_track_hash seen in query profiles. Queries are hashed to integer values in order to look up associated rowcounts.

ROWCOUNT_INITIALIZED

Boolean flag indicating whether the entry has a rowcount associated with it. This may be false if the entry is tied to a sampling query that has not yet finished.

ROWCOUNT

Rowcount associated with the entry.

HIT_COUNT

Total number of times the entry has been written to and read from once rowcounts have been initialized.

QUERY_TEXT

This column is empty by default to save memory. Once enable_cross_query_stats_store_query_text is enabled, the query text associated with the entry. Currently works for sampling queries only.

LAST_HIT_TIME

The last time the entry was used, either by reading from it or writing to it. The time is based on the number of ticks since the server started up. There is no conversion to a Unix timestamp.

LAST_UPDATE_TIME

The last time the entry was written to. The time is based on the number of ticks since the server started up. There is no conversion to a Unix timestamp.

ADDED_TIME

The time the entry was created. The time is based on the number of ticks since the server started up. There is no conversion to a Unix timestamp.

In addition to these columns, which are the same columns for CROSS_QUERY_STATS_CACHE, this managed view includes node‑level columns that mirror the definitions used in the MV_NODES managed view:

Column Name

Description

NODE_ID

The ID of the node. This ID matches the node_id reported for tasks running on the node.

IP_ADDR

The IP address of the node.

PORT

The port on which the node is listening.

TYPE

The type of a given node: MA, leaf, or CA.

Last modified:

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