Durability with BookKeeper
Authors:
Open Access
- 29 January 2013
- journal article
- Published by Association for Computing Machinery (ACM) in ACM SIGOPS Operating Systems Review
- Vol. 47 (1) , 9-15
Abstract
Practical systems must often guarantee that changes to the system state are durable. Examples of such systems are databases, file systems, and messaging middleware with guaranteed delivery. One common way of implementing durability while keeping performance high is to use a log to persist updates to the system state. Such systems use the log to reconstruct the system state in the event of a crash. When implementing such a log, if the log is only stored locally, the system state is permanently lost when the server writing the log experiences a permanent hardware failure. BookKeeper is a system that exposes a log abstraction for building high performance, highly available distributed systems. BookKeeper transparently implements replication for high availability and striping for high performance. A Book- Keeper deployment comprises storage servers called bookies, which are designed to serve a large number of concurrent ledgers. BookKeeper is currently an open-source project and is in production use at Yahoo!Keywords
This publication has 14 references indexed in Scilit:
- BigtableACM Transactions on Computer Systems, 2008
- Byzantine disk paxos2004
- Unreliable failure detectors for reliable distributed systemsJournal of the ACM, 1996
- Distributed logging for transaction processingACM SIGMOD Record, 1987
- Reimplementing the Cedar file system using logging and group commitACM SIGOPS Operating Systems Review, 1987
- A quorum-consensus replication method for abstract data typesACM Transactions on Computer Systems, 1986
- The Alpine file systemACM Transactions on Computer Systems, 1985
- Principles of transaction-oriented database recoveryACM Computing Surveys, 1983
- A history and evaluation of System RCommunications of the ACM, 1981
- Notes on data base operating systems1978