Instant Recovery with Write-Ahead Logging: Page Repair, System Restart, and Media Restore

Graefe, Goetz; Guy, Wey; Sauer, Caetano

doi:10.2200/s00617ed1v01y201411dtm039

Cited by 10 publications

(2 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The second deficiency is addressed with the instant restore technique, which was first described in earlier work [32] and discussed in more detail, implemented, and evaluated in this paper. By generalizing single-pass restore and other recovery methods such as single-page repair, instant restore is the first media recovery method to effectively eliminate the two deficiencies discussed.…”

Section: Discussionmentioning

confidence: 99%

Instant Restore After a Media Failure

Sauer

Graefe

Härder

2017

Advances in Databases and Information Systems

Self Cite

View full text Add to dashboard Cite

Media failures usually leave database systems unavailable for several hours until recovery is complete, especially in applications with large devices and high transaction volume. Previous work introduced a technique called single-pass restore, which increases restore bandwidth and thus substantially decreases time to repair. Instant restore goes further as it permits read/write access to any data on a device undergoing restoreeven data not yet restored-by restoring individual data segments on demand. Thus, the restore process is guided primarily by the needs of applications, and the observed mean time to repair is effectively reduced from several hours to a few seconds.This paper presents an implementation and evaluation of instant restore. The technique is incrementally implemented on a system starting with the traditional ARIES design for logging and recovery. Experiments show that the transaction latency perceived after a media failure can be cut down to less than a second and that the overhead imposed by the technique on normal processing is minimal. The net effect is that a few "nines" of availability are added to the system using simple and lowoverhead software techniques.

show abstract

Section: Discussionmentioning

confidence: 99%

Instant Restore After a Media Failure

Sauer

Graefe

Härder

2017

Advances in Databases and Information Systems

Self Cite

View full text Add to dashboard Cite

show abstract

“…WBL also does not require an WALstyle undo phase. Instead, the DBMS only tracks the transactions active in the current group commit interval as determined by the analysis phase, so that it can ignore the effects of the associated uncommitted transactions [15,44,46]. In case of a transaction failure, the transaction manager rolls back any dirty changes flushed to NVM using the meta-data that it records in the dirty tuple table.…”

Section: Logging and Recoverymentioning

confidence: 99%

How to Build a Non-Volatile Memory Database Management System

Arulraj

Pavlo

2017

Proceedings of the 2017 ACM International Conference on Management of Data

View full text Add to dashboard Cite

The difference in the performance characteristics of volatile (DRAM) and non-volatile storage devices (HDD/SSDs) influences the design of database management systems (DBMSs). The key assumption has always been that the latter is much slower than the former. This affects all aspects of a DBMS's runtime architecture. But the arrival of new non-volatile memory (NVM) storage that is almost as fast as DRAM with fine-grained read/writes invalidates these previous design choices. In this tutorial, we provide an outline on how to build a new DBMS given the changes to hardware landscape due to NVM. We survey recent developments in this area, and discuss the lessons learned from prior research on designing NVM database systems. We highlight a set of open research problems, and present ideas for solving some of them. 1 NVM is also referred to as storage-class memory or persistent memory.

show abstract