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.

DISTRIBUTED_DATABASES

This view contains information about databases.

Column Name

Description

DATABASE_ID

The unique ID of a given database.

DATABASE_NAME

The name of a given database.

NUM_PARTITIONS

The number of a partitions in a given database.

NUM_SUB_PARTITIONS

The number of sub-partitions in a given database.

CLUSTER_ID

The ID of the related cluster for a given database.

REMOTE_NAME

The remote name of a given database.

IS_SYNC

Determines if the database uses synchronous replication for high availability.

IS_SYNC_DURABILITY

Determines if the database uses synchronous durability.

IS_PAUSED

Whether DR replication of a given database is paused.

SITE_ID

The ID for the cluster.

IS_SYNC_DURABILITY_ON_REF_DB_ONLY

Indicates whether the reference database is sync durable despite the partition databases being async durable.

STORAGE_ID

Storage ID of the database.

SAFE_TS

The lower bound of the pre-prepare timestamps of any unresolved 2PC their participants (reference and partition databases) participate or will participate in.

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