MV_BOTTOMLESS_SUMMARY

Warning

SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.

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_AVAILABILIT`Y	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.

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 |
+------------------------+-------------------+--------------------+--------------------------------+--------------------------------+----------------------+----------------------+-----------------------+
|                    0.3 |  65.8199313476182 | Success            |               4.39891453458896 |             131.24585362684732 |               0.9862 |     68.3373684189926 |                     0 |
+------------------------+-------------------+--------------------+--------------------------------+--------------------------------+----------------------+----------------------+-----------------------+

MV_BOTTOMLESS_SUMMARY

Was this article helpful?

Was this article helpful?