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.

Aggregator Failover

On this page

Primary Cluster Master Aggregator Failure

If the master aggregator on the primary cluster fails, no changes to reference data or database schemas can be made. DML changes to distributed tables can be made through the child aggregators, and these changes are replicated to the secondary cluster.

If you can bring the master aggregator back online, replication of reference data and database schema changes will automatically continue. Otherwise, you can failover to a child aggregator using PROMOTE AGGREGATOR … TO MASTER.

Secondary Cluster Master Aggregator Failure

If the master aggregator on the secondary cluster fails, no changes to reference data or database schemas on the primary cluster will be replicated to the secondary cluster. DML changes to distributed tables can be made through the child aggregators on the primary cluster, and these changes are replicated to the secondary cluster.

If you can bring the master aggregator back online, replication of reference data and database schema changes from the primary cluster will automatically continue. Otherwise, you can failover to a child aggregator using PROMOTE AGGREGATOR … TO MASTER.

Last modified:

Was this article helpful?

On this page

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