MetaCartSign in to MyCiteSeer

Include Citations | Advanced Search | Help

Include Citations | Advanced Search | Help

  Minimal byzantine storage (2002) [45 citations — 4 self]

Download:
pdf
by Lorenzo Alvisi, Michael Dahlin
In Proceedings of the 16th International Symposium on Distributed Computing (DISC
http://www.cs.utexas.edu/users/lorenzo/papers/MinByz-TR.pdf
Add To MetaCart

Abstract:

Abstract. Byzantine fault-tolerant storage systems can provide high availability in hazardous environments, but the redundant servers they require increase software development and hardware costs. In order to minimize the number of servers required to implement fault-tolerant storage services, we develop a new algorithm that uses a "Listeners " pattern of network communication to detect and resolve ordering ambiguities created by concurrent accesses to the system. Our protocol requires 3f+ 1 servers to tolerate up to f Byzantine faults--f fewer than the 4f + 1 required by existing protocols for non-self-verifying data. In addition, SBQ-L provides atomic consistency semantics, which is stronger than the regular or pseudo-atomic semantics provided by these existing protocols. We show that this protocol is optimal in the number of servers--any protocol that provides safe semantics or stronger requires at least 3f + 1 servers to tolerate f Byzantine faults in an asynchronous system. We also examine protocols that store self-verifying data (i.e. data that cannot be undetectably altered). Existing protocols can use self-verifying data to reduce the number of servers required to tolerate faults but because SBQ-L already uses the minimum possible number of servers for its semantics, self-verifying data provides no advantage. Finally, we examine a non-confirmable writes variation of the SBQ-L protocol where a client cannot determine when its writes complete. We show that SBQ-L with non-confirmable writes provides regular semantics with 2f + 1 servers and that this number of servers is minimal.

Citations

1747 Time, clocks and the ordering of events in a distributed system – Lamport - 1978
1074 Impossibility of distributed consensus with one faulty process – Fischer, Lynch, et al. - 1985
625 Design Patterns – Gamma, Helm, et al. - 1995
353 Practical byzantine fault tolerance – Castro, Liskov - 1999
284 Byzantine quorum systems – Malkhi, Reiter - 1998
112 On Interprocess Communication – Lamport - 1986
68 Secure and scalable replication in phalanx – Malkhi, Reiter - 1998
62 A.: The load, capacity, and availability of quorum systems – Naor, Wool - 1998
50 Using abstraction to improve fault tolerance – BASE - 2001
44 The load and availability of Byzantine quorum systems – Malkhi, Reiter, et al. - 2000
31 Consistency in a partitioned network: a survey – Davidson, Garcia-Molina, et al. - 1985
25 Authenticated Byzantine fault tolerance without public-key cryptography – Castro, Liskov - 1999
22 D.: Sharing memory robustly in message passing systems – Attiya, Bar-Noy, et al. - 1996
20 Synchronous Byzantine quorum systems – Bazzi - 1997
10 Access cost for asynchronous Byzantine quorum systems – Bazzi - 2001
6 Time, clocks, and the ordering of events in a distributed system – Lampoft - 1978
5 A recipe for atomic semantics for Byzantine quorum systems – Pierce, Alvisi - 2000
2 On interprocess communications – Lainport - 1986
2 Time, clocks, and the ordering of events in a distributed system – Lainport - 1978
1 On interprocess communications – Lampoft - 1986