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_CLUSTER_STATUS

This view stores information about partitions within a cluster.

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

Column Name

Description

NODE_ID

The ID of the related node.

HOST

The hostname or IP address for the related leaf node.

PORT

The port number of the related leaf node.

DATABASE_NAME

The name of the related database.

ROLE

The role of the related database (orphan, master, child, or reference).

STATE

The state of the related database (online, offline, replicating).

POSITION

A number indicating the position in the transaction log.

MASTER_HOST

The hostname or IP address for the related master aggregator.

MASTER_PORT

The port number of the related master aggregator.

METADATA_MASTER_NODE_ID

The ID of the master aggregator node expected by the metadata.

METADATA_MASTER_HOST

The hostname or IP address for the related master aggregator expected by the metadata.

METADATA_MASTER_PORT

The port number of the related master aggregator expected by the metadata.

METADATA_ROLE

The role of the related database expected by the metadata.

DETAILS

An optional message about the current state.

COMMITTED_POSITION

The position up to which each transaction has been committed. All pages in the log before this LSN are confirmed to be committed.

HARDENED_POSITION

The current position in the transaction log on disk. All pages in the log before this LSN are written to disk.

REPLAY_POSITION

The position up to which changes have been applied to replica. All pages before this LSN have been replayed into memory.

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