SingleStore DB

Durability

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 DB 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.

Notice

Database 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 DB 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.