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.

Disaster Recovery

Disaster Recovery (DR), which is based on REPLICATE DATABASE, can be enabled when running SingleStore on Kubernetes.

Users may declare a replicationSpec section to enable replication and DR. This is an optional section that can be added to the sdb-cluster.yaml file of the primary and secondary clusters to enable replication and DR between them, and to specify which connection model should be used.

replicationSpec:
  enable: true
  connectivity: viaHost

To support replication and DR, either of the two following requirements must be met by the underlying infrastructure:

  • Kubernetes hosts in primary and secondary clusters can reach each other via host IPs across clusters

  • Kubernetes pods in primary and secondary clusters can reach each other via pod IPs across clusters

In addition, the following requirements must be met:

  • SingleStore 7.1.3 or later must be deployed on both the primary and secondary clusters

  • The primary and secondary clusters’ DDL endpoints are stable

Valid values for the fields in replicationSpec are:

  • For the enable field: true, false

  • For the connectivity field: viaHost, viaPod

    • Use viaHost when Kubernetes hosts in primary and secondary clusters can reach each other via host IPs across clusters

    • Use viaPod when Kubernetes pods in primary and secondary clusters can reach each other via pod IPs across clusters

Refer to REPLICATE DATABASE for more information.

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