Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10, while SingleStore 9.0 is recommended for production workloads.

MV_BLOB_CACHE_EVENTS

This view stores information about events pertaining to cached blobs.

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

Column Name

Description

NODE_ID

ID of the related node.

EVENT_TYPE

Either fetch or eviction:

  • fetch - downloading a columnar blob file from S3.

  • eviction - deleting the blob file because it can be retrieved again from S3 later if necessary.

DATABASE_NAME

The name of the related database.

ORDINAL

The partition ordinal of the database, if relevant.

FILE_NAME

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

FILE_SIZE

The size of the blob, in bytes.

UNIX_TIMESTAMP

Timestamp of the event.

FETCH_TIME_TAKEN_MS

Only applies for fetches. The time in milliseconds spent waiting on network for the blob fetch. This does not track time spent waiting for other fetches to complete before submitting the fetch for this blob.

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