MV_CACHED_BLOBS

This view stores information about currently cached blobs.

Learn more about interpreting this view in the Components to Monitor guide.

Column Name

Description

NODE_ID

The ID of the node on which the blob is cached.

FILE_NAME

The on-disk filename of the blob (not the S3 path).

DATABASE_NAME

The name of the related database.

ORDINAL

The partition ordinal of the database, if relevant.

STATUS

The status of the blob:

  • Fetch error. Fetch will be retried on next request.

  • Cached

  • Downloading

MOST_RECENT_TIMESTAMP_TICKS

The internal timestamp of the most recent scan access to the blob. This is the primary timestamp used for LRU2 eviction.

SECOND_MOST_RECENT_TIMESTAMP_TICKS

The internal timestamp of the second most recent scan access to the blob. This is the tie-breaker timestamp used for LRU2 eviction.

EVICTABLE

Whether the blob can be evicted (Yes or No). A blob is not evictable while a query references it or before it has been uploaded to S3.

SIZE

The size of the blob, in bytes.

TYPE

Whether the blob belongs to a primary or replica partition of the database (Primary or Replica).

Last modified:

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.