Sign inTry Free

Durability

On this page

In-memory database updates you make using Data Definition Language DDL and Data Manipulation Language DML commands are also durable; they are saved to the log on disk. Following a server restart, SingleStore recovers the server’s database partitions by loading them from the log to memory.

Synchronous and Asynchronous Durability

When you use the CREATE DATABASE, RESTORE DATABASE, and REPLICATE DATABASE commands, you can specify whether to use synchronous or asynchronous durability. Synchronous updates to the log on disk will complete before the commit of the transaction is acknowledged to the client application.

If the disk containing the log runs out of space, the database update transaction rolls back; no in-memory update is made.

Note

Database durability (SYNC DURABILITY) cannot be disabled. The reference for the CREATE DATABASE, RESTORE DATABASE, and REPLICATE DATABASE commands explains whether synchronous or asynchronous durability is used if this durability setting is not specified.

Recovery

Following a server restart, SingleStore loads the server’s database partitions from disk to memory. During this process, the databases are in the recovery state.

Run SHOW DATABASES with the EXTENDED option to see which databases are recovering and to get an estimate for how long recovery will take.

You cannot connect to a database while it is recovering.

Last modified: November 17, 2022

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