Sign inTry Free

Durability

On this page

What is the durability guaranteed by SingleStore Helios?

SingleStore Helios provides several options to control the trade-offs between performance and durability. In its most durable state, SingleStore Helios will not lose any transactions that have been acknowledged.

Transaction writes are replicated on two nodes before commit, to ensure updates are never lost in case of single-node failure thereby ensuring durability.

See CREATE DATABASE for more information.

Can I configure SingleStore Helios to be fully durable?

Yes, you can configure the durability through the WITH {SYNC | ASYNC} DURABILITY option in the CREATE DATABASE and RESTORE DATABASE commands.

What isolation levels does SingleStore Helios provide?

SingleStore Helios provides the READ COMMITTED isolation level. This guarantees that no transaction will read any uncommitted data from another transaction. Furthermore, once a change is observed in one transaction, it will be visible to all transactions.

Unlike the REPEATABLE READ isolation level, READ COMMITTED isolation level does not guarantee that a row will remain the same for every read query in a given transaction. Applications that use SingleStore Helios should take this into account.

What happens if the hardware SingleStore Helios runs on fails?

SingleStore is built on a cloud-native and highly resilient architecture that features high availability within the workspace. When cloud instances fail, SingleStore transparently handles the failures, replaces instances, and maintains workspace availability to the application.

Last modified: January 10, 2023

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