Sign inTry Free

Important

New database features are no longer connected to engine versions; features are now enabled independently during scheduled update windows, and “major” and “minor” releases no longer exist in Helios. Please visit the release notes to view the latest features available in your database clusters.

MV_BOTTOMLESS_STATUS

This view gives an overview of all the unlimited storage databases in a cluster, includes the reference databases and the partition databases.

It gives information about the databases location including the node/host/port, where the storage is located (storage_directory/bucket), as well as upload details.

Column name

Description

DATABASE_NAME

Name of the database.

STORAGE_ID

Storage ID of the database.

COMPUTE_ID

Compute ID of the database.

COMPUTE_STATE

Values can be 'Legacy', 'Broken', or 'Full' which indicates: none, unhealthy, or healthy.

STORAGE_DIRECTORY

Remote storage directory for the database.

BUCKET

Remote storage bucket for the database.

ROLE

Current role of the database (primary / secondary / offline).

TERM

A unique identifier of the current master instance of the database.

LOG_PERSISTED_LSN

Log sequence number below which all log chunks have been permanently stored to remote storage.

COMMIT_LSN

Position in the log before which all pages have been committed. All content is committed in the pages that are in the log before this log sequence number (LSN).

UPLOAD_QUEUE_WAIT_SECS

Number of seconds by which the uploads to remote storage are behind (delayed), in seconds.

UPLOAD_MB_PER_SEC

Rate at which files are being uploaded to remote storage, in seconds.

NODE_ID

ID of the node where the database is located.

HOST

Host of the node where the database is located.

PORT

Port of the node where the database is located.

ORDINAL

Ordinal of the database if it is a partition database, NULL for reference database.

Example:

SELECT * FROM information_schema.MV_BOTTOMLESS_STATUS;
+---------------+------------------------+------------------------+---------------+----------------------------------------------+----------+---------+------------------+-------------------+------------+------------------------+-------------------+---------+-----------+-------+---------+
| DATABASE_NAME | STORAGE_ID             | COMPUTE_ID             | COMPUTE_STATE |  STORAGE_DIRECTORY                           | BUCKET   | ROLE    | TERM             | LOG_PERSISTED_LSN | COMMIT_LSN | UPLOAD_QUEUE_WAIT_SECS | UPLOAD_MB_PER_SEC | NODE_ID | HOST      | PORT  | ORDINAL |
+---------------+------------------------+------------------------+---------------+----------------------------------------------+----------+---------+------------------+-------------------+------------+------------------------+-------------------+---------+-----------+-------+---------+
| x_db          | 10930645997319398241:1 | 10930645997319398241:1 | Legacy        |  cadccdac/10930645997319398241_1/ref         | s3bucket | replica | 2251799813685329 | 0                 | 2          | 0                      | NULL              | 3       | 127.0.0.1 | 10002 | NULL    |
| x_db          | 10930645997319398241:1 | 10930645997319398241:1 | Legacy        |  acdcadcc/10930645997319398241_1/partition_0 | s3bucket | replica | 2251799813685330 | 0                 | 1          | 0                      | NULL              | 3       | 127.0.0.1 | 10002 | 0       |
| x_db          | 10930645997319398241:1 | 10930645997319398241:1 | Legacy        |  abcdcddd/10930645997319398241_1/partition_1 | s3bucket | master  | 2251799813685331 | 0                 | 2          | 0                      | 0                 | 3       | 127.0.0.1 | 10002 | 1       |
| x_db          | 10930645997319398241:1 | 10930645997319398241:1 | Legacy        |  cadccdac/10930645997319398241_1/ref         | s3bucket | master  | 2251799813685329 | 0                 | 3          | 0                      | 0                 | 1       | 127.0.0.1 | 10000 | NULL    |
| x_db          | 10930645997319398241:1 | 10930645997319398241:1 | Legacy        |  cadccdac/10930645997319398241_1/ref         | s3bucket | replica | 2251799813685329 | 0                 | 2          | 0                      | NULL              | 2       | 127.0.0.1 | 10001 | NULL    |
| x_db          | 10930645997319398241:1 | 10930645997319398241:1 | Legacy        |  acdcadcc/10930645997319398241_1/partition_0 | s3bucket | master  | 2251799813685330 | 0                 | 2          | 0                      | 0                 | 2       | 127.0.0.1 | 10001 | 0       |
| x_db          | 10930645997319398241:1 | 10930645997319398241:1 | Legacy        |  abcdcddd/10930645997319398241_1/partition_1 | s3bucket | replica | 2251799813685331 | 0                 | 1          | 0                      | NULL              | 2       | 127.0.0.1 | 10001 | 1       |
+---------------+------------------------+------------------------+---------------+----------------------------------------------+----------+---------+------------------+-------------------+------------+------------------------+-------------------+---------+-----------+-------+---------+

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