From 01a8a2a1419221cc0d9d4d7536101e87c7798d69 Mon Sep 17 00:00:00 2001 From: Philip O'Toole Date: Sat, 12 Jun 2021 18:04:22 -0400 Subject: [PATCH] Update DESIGN.md --- DOC/DESIGN.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DOC/DESIGN.md b/DOC/DESIGN.md index eb7c59d7..9dd03cc9 100644 --- a/DOC/DESIGN.md +++ b/DOC/DESIGN.md @@ -34,7 +34,7 @@ The diagram below shows a high-level view of an rqlite node. The Raft layer always creates a file -- it creates the _Raft log_. The log stores the set of committed SQLite commands, in the order which they were executed. This log is authoritative record of every change that has happened to the system. It may also contain some read-only queries as entries, depending on read-consistency choices. ### SQLite -By default the SQLite layer doesn't create a file. Instead it creates the database in RAM. rqlite can create the SQLite database on disk, if so configured at start-time. +By default the SQLite layer doesn't create a file. Instead it creates the database in memory. rqlite can create the SQLite database on disk, if so configured at start-time, by passing `-on-disk` to `rqlited` at startup. Regardless of whether rqlite creates a database entirely in memory, or on disk, the SQLite database is completely recreated everytime `rqlited` starts, using the information stored in the Raft log. ## Log Compaction and Truncation rqlite automatically performs log compaction, so that disk usage due to the log remains bounded. After a configurable number of changes rqlite snapshots the SQLite database, and truncates the Raft log. This is a technical feature of the Raft consensus system, and most users of rqlite need not be concerned with this.