Using Asynchronous Replication with Synchronous Durability is not Allowed

You cannot use asynchronous replication with synchronous durability. With asynchronous replication, after a transaction commits, data is replicated from the primary to the replica partitions, with a possible delay. A crash of the primary partitions would cause the replica partitions to be promoted to primaries, resulting in possible data loss due to asynchronous replication. If the transaction were to have synchronous durability, it would commit on the replicas only after the logs on the replicas were saved; yet if the primaries failed, data could still be lost when failing over to the replicas. So taking the time to save the logs on the replicas has no expected benefit. Hence, it is not allowed.

Last modified: June 13, 2024

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