A system architecture for enhanced availability of tightly coupled distributed systems

We present a system architecture which facilitates enhanced availability of tightly coupled distributed systems by temporarily relaxing constraint consistency. Three different types of consistency are distinguished in tightly coupled distributed systems - replica consistency, concurrency consistency, and constraint consistency. Constraint consistency defines the correctness of the system with respect to a set of data integrity rules (application defined predicates). Traditional systems either guarantee strong constraint consistency or no constraint consistency at all. However, a class of systems exists, where data integrity can be temporarily relaxed in order to enhance availability, i.e. constraint consistency can be traded against availability. This allows for a context- and situation-specific optimum of availability. This paper presents the basic concepts of the trading process and the proposed system architecture to enable a fine-grained tuning of the trade-off in tightly coupled distributed systems.

[1]  Keith Marzullo,et al.  Highly-available services using the primary-backup approach , 1992, [1992 Proceedings] Second Workshop on the Management of Replicated Data.

[2]  M. Rott,et al.  Innovation and the Knowledge Economy : Issues , Applications , Case Studies , 2005 .

[3]  Leslie Lamport,et al.  Proving the Correctness of Multiprocess Programs , 1977, IEEE Transactions on Software Engineering.

[4]  Maurice Herlihy,et al.  Linearizability: a correctness condition for concurrent objects , 1990, TOPL.

[5]  William H. Sanders,et al.  AQuA: An Adaptive Architecture that Provides Dependable Distributed Objects , 2003, IEEE Trans. Computers.

[6]  Rachid Guerraoui,et al.  System support for object groups , 1998, OOPSLA '98.

[7]  Pablo Galdámez,et al.  Extended Membership Problem for Open Groups: Specification and Solution , 2004, VECPAR.

[8]  Flaviu Cristian,et al.  Understanding fault-tolerant distributed systems , 1991, CACM.

[9]  Paulo Veríssimo,et al.  Distributed Systems for System Architects , 2001, Advances in Distributed Computing and Middleware.

[10]  Rachid Guerraoui,et al.  Software-Based Replication for Fault Tolerance , 1997, Computer.

[11]  TECHN. MEHDI JAZAYERI,et al.  Trading Consistency for Availability in a Replicated System , 2004 .

[12]  Fred B. Schneider,et al.  The primary-backup approach , 1993 .

[13]  Amin Vahdat,et al.  Design and evaluation of a conit-based continuous consistency model for replicated services , 2002, TOCS.

[14]  Fred B. Schneider,et al.  Replication management using the state-machine approach , 1993 .

[15]  Carl E. Landwehr,et al.  Basic concepts and taxonomy of dependable and secure computing , 2004, IEEE Transactions on Dependable and Secure Computing.

[16]  Robert H. Thomas,et al.  A Majority consensus approach to concurrency control for multiple copy databases , 1979, ACM Trans. Database Syst..

[17]  Jim Gray,et al.  A critique of ANSI SQL isolation levels , 1995, SIGMOD '95.

[18]  Gustavo Alonso,et al.  Web Services , 2004, Data-Centric Systems and Applications.

[19]  Bharat K. Bhargava,et al.  Replication Techniques in Distributed Systems , 1996, Advances in Database Systems.

[20]  Sam Toueg,et al.  Fault-tolerant broadcasts and related problems , 1993 .

[21]  Karl M. Göschka,et al.  Fault-tolerance in a distributed management system: a case study , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[22]  Kenneth P. Birman,et al.  Understanding partitions and the 'no partition' assumption , 1993, 1993 4th Workshop on Future Trends of Distributed Computing Systems.

[23]  Mesaac Makpangou,et al.  A Generic and Flexible Model for Replica Consistency Management , 2004, ICDCIT.

[24]  Priya Narasimhan,et al.  Reconciling Replication and Transactions for the End-to-End Reliability of CORBA Applications , 2002, CoopIS/DOA/ODBASE.