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_AGGREGATED_REPLICATION_STATUS

This view provides the aggregated replication status of each database in the cluster.

Each row in this view corresponds to a specific type of replication (DR/non-DR) for each database in the cluster. This view can be accessed from any aggregator (MA or CA).

Column name

Description

is_dr

Specifies if the row corresponds to a DR replication link.

is_sync

Specifies if the row corresponds to a synchronous replication link.

database_name

The name of the database in the current host.

primary_uri

The URI of the primary cluster’s MA in the host:port/source_db_name format.

secondary_uri

The URI of the secondary cluster’s MA in the host:port/source_db_name format.

primary_state

The replication state of the primary cluster.

secondary_state

The replication state of the secondary cluster.

lsn_lag

The total number of LSNs lagging to catch up with the primary cluster from all nodes.

volume_lag_mb

The total volume of lag, in megabytes (MB), from all nodes.

replication_throughput_mbps

The total throughput, in megabytes per second (MB/s), from all nodes.

estimated_catcup_time_s

The maximum time, in seconds, required by the secondary cluster to catch up with the primary cluster from all nodes.

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