Sign inTry Free

MV_BOTTOMLESS_SUMMARY

This view is an at-a-glance rollup table the shows what is happening at the moment with the unlimited storage cluster.

It consolidates a lot of the detailed information in the MV_BOTTOMLESS_STATUS_EXTENDED view and displays it in one smaller, easy to read table.

Column name

Description

UPLOAD_QUEUE_WAIT_SECS

Number of seconds the uploads to remote storage are delayed in the entire cluster.

UPLOAD_MB_PER_SEC

The rate at which files are being uploaded to remote storage in the entire cluster.

LAST_UPLOAD_RESULT

If all partitions in the cluster report SUCCESS for upload, then this reports SUCCESS.

BLOB_CACHE_DOWNLOAD_MB_PER_SEC

Rate at which the blob cache is downloading files from remote storage in the entire cluster.

BLOB_CACHE_EVICTION_MB_PER_SEC

Rate at which the blob cache is evicting files in the entire cluster, per second.

OLDEST_DATA_AGE_DAYS

Age of the oldest piece of data in the entire cluster.

API_REQUESTS_PER_SEC

Rate of API requests made to remote storage in the entire cluster.

IS_BEING_RATE_LIMITED

Indicates whether any node in the entire cluster is being rate limited on API requests to remote storage. On S3, rate limiting starts when we receive 503 SLOWDOWN errors.

BOTTLE_SERVICE_AVAILABILITY

Number of successful bottle service api calls per second to the total number of bottle service api calls per second (success + failed) over the last 30 seconds. It is calculated as: BOTTLE_SERVICE_AVAILABILITY = SUCCESS_BOTTLE_SERVICE_API_PER_SECOND / (SUCCESS_BOTTLE_SERVICE_API_PER_SECOND + FAILED_BOTTLE_SERVICE_API_PER_SECOND)

OBJECT_STORE_AVAILABILITY

Number of successful bottomless api calls per second to the total number of bottomless api calls per second (success + failed) over the last 30 seconds. It is calculated as: OBJECT_STORE_AVAILABILITY = SUCCESS_API_PER_SECOND / (SUCCESS_API_PER_SECOND + FAILED_API_PER_SECOND)

IS_BOTTLE_SERVICE_UP

Shows false if any node's bottle service heartbeat is down.

BOTTLE_SERVICE_UPTIME_DOWNTIME_SECS

Shows the maximum downtime (in seconds) if any node's bottle service heartbeat is down, else if all node's bottle service heartbeat is up, it shows the minimum uptime.

UPLOAD_BLOB_LEAD_PAGES

Specifies the amount of log data queued for upload but not yet persisted to the remote storage. This is calculated as the difference between the maximum of BLOB_PERSISTED_LSN and LOG_PERSISTED_LSN from MV_BOTTOMLESS_STATUS_EXTENDED information schema view.

Example:

SELECT * FROM information_schema.MV_BOTTOMLESS_SUMMARY;
+------------------------+-------------------+--------------------+--------------------------------+--------------------------------+----------------------+----------------------+-----------------------+---------------------------+-----------------------------+----------------------+-------------------------------------+------------------------+
| UPLOAD_QUEUE_WAIT_SECS | UPLOAD_MB_PER_SEC | LAST_UPLOAD_RESULT | BLOB_CACHE_DOWNLOAD_MB_PER_SEC | BLOB_CACHE_EVICTION_MB_PER_SEC | OLDEST_DATA_AGE_DAYS | API_REQUESTS_PER_SEC | IS_BEING_RATE_LIMITED | OBJECT_STORE_AVAILABILITY | BOTTLE_SERVICE_AVAILABILITY | IS_BOTTLE_SERVICE_UP | BOTTLE_SERVICE_UPTIME_DOWNTIME_SECS | UPLOAD_BLOB_LEAD_PAGES |
+------------------------+-------------------+--------------------+--------------------------------+--------------------------------+----------------------+----------------------+-----------------------+---------------------------+-----------------------------+----------------------+-------------------------------------+------------------------+
|                      0 |                 0 | Success            |                              0 |                              0 |               6.9887 |   0.3706105867031148 |                     0 |                         1 |                           1 |                    1 |                                1484 |                      2 |
+------------------------+-------------------+--------------------+--------------------------------+--------------------------------+----------------------+----------------------+-----------------------+---------------------------+-----------------------------+----------------------+-------------------------------------+------------------------+

Last modified: June 11, 2025

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