Repository logo
Log in(current)
Repository logoMIT Open ScholarshipDSpace@MIT
  1. Home
  2. Computer Science and Artificial Intelligence Lab (CSAIL)
  3. CSAIL Digital Archive
  4. CSAIL Technical Reports (July 1, 2003 - present)
  5. Detecting and Tolerating Byzantine Faults in Database Systems

Detecting and Tolerating Byzantine Faults in Database Systems

Thumbnail Image
Download
Name

MIT-CSAIL-TR-2008-040.ps

Size

72.14 KB

Format

PostScript

Checksum (MD5)

9b51f0716d8060f15c2a0756d3fea8b2

Thumbnail Image
Download
Name

MIT-CSAIL-TR-2008-040.pdf

Size

770.3 KB

Format

Adobe PDF

Checksum (MD5)

101731dcd701ec68b5a37169eec6b903

Author(s)
Vandiver, Benjamin Mead
Advisor(s)
Barbara Liskov
Date Issued
June 30, 2008
Abstract
This thesis describes the design, implementation, and evaluation of a replication scheme to handle Byzantine faults in transaction processing database systems. The scheme compares answers from queries and updates on multiple replicas which are off-the-shelf database systems, to provide a single database that is Byzantine fault tolerant. The scheme works when the replicas are homogeneous, but it also allows heterogeneous replication in which replicas come from different vendors. Heterogeneous replicas reduce the impact of bugs and security compromises because they are implemented independently and are thus less likely to suffer correlated failures. A final component of the scheme is a repair mechanism that can correct the state of a faulty replica, ensuring the longevity of the scheme.The main challenge in designing a replication scheme for transaction processingsystems is ensuring that the replicas state does not diverge while allowing a high degree of concurrency. We have developed two novel concurrency control protocols, commit barrier scheduling (CBS) and snapshot epoch scheduling (SES) that provide strong consistency and good performance. The two protocols provide different types of consistency: CBS provides single-copy serializability and SES provides single-copy snapshot isolation. We have implemented both protocols in the context of a replicated SQL database. Our implementation has been tested with production versions of several commercial and open source databases as replicas. Our experiments show a configuration that can tolerate one faulty replica has only a modest performance overhead (about 10-20% for the TPC-C benchmark). Our implementation successfully masks several Byzantine faults observed in practice and we have used it to find a new bug in MySQL.
Persistent DSpace Link
http://hdl.handle.net/1721.1/41873
Repository logo
PrivacyPermissionsAccessibilityContact us
Repository logo
Notify us about copyright concerns.