MM-DIRECT Main memory database instant recovery with tuple consistent checkpoint

Main memory databases (MMDBs) technology handles the primary database in Random Access Memory (RAM) to provide high throughput and low latency. However, volatile memory makes MMDBs much more sensitive to system failures. The contents of the database are lost in these failures, and, as a result, syst...

Full description

Saved in:
Bibliographic Details
Published in:The VLDB journal Vol. 33; no. 3; pp. 859 - 882
Main Authors: Magalhaes, Arlino, Brayner, Angelo, Monteiro, Jose Maria
Format: Journal Article
Language:English
Published: Berlin/Heidelberg Springer Berlin Heidelberg 01.05.2024
Subjects:
Computer Science
Database Management
Regular Paper
Database
System failure
Instant recovery
Main memory database
In-memory database
ISSN:1066-8888, 0949-877X
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Main memory databases (MMDBs) technology handles the primary database in Random Access Memory (RAM) to provide high throughput and low latency. However, volatile memory makes MMDBs much more sensitive to system failures. The contents of the database are lost in these failures, and, as a result, systems may be unavailable for a long time until the database recovery process has been finished. Therefore, novel recovery techniques are needed to repair crashed MMDBs as quickly as possible. This paper presents MM-DIRECT (Main Memory Database Instant RECovery with Tuple consistent checkpoint), a recovery technique that enables MMDBs to schedule transactions simultaneously with the database recovery process at system startup. Thus, it gives the impression that the database is instantly restored. The approach implements a tuple-level consistent checkpoint to reduce the recovery time. To validate the proposed approach, experiments were performed in a prototype implemented on the Redis database. The results show that the instant recovery technique effectively provides high transaction throughput rates even during the recovery process and normal database processing.
ISSN:1066-8888
0949-877X
DOI:10.1007/s00778-024-00846-z