A Recovery Protocol for Middleware Replicated Databases Providing GSI

Middleware database replication is a way to increase availability and afford site failures for dynamic content Websites. There are several replication protocols that ensure data consistency for these systems. The most attractive ones are those providing generalized snapshot isolation (GSI), as read operations never block. These replication protocols are based on the certification process, however, up to our knowledge, they do not cope with the recovery of a replica. In this paper we propose a recovery protocol that ensures GSI (we provide an outline of its correctness) that does not interfere with user transactions and permits the execution of transactions in the recovering node, even though the recovery process has not finished

[1]  Gustavo Alonso,et al.  Database replication techniques: a three parameter classification , 2000, Proceedings 19th IEEE Symposium on Reliable Distributed Systems SRDS-2000.

[2]  Marta Patiño-Martínez.  Consistent Database Replication at the Middleware Level , 2005 .

[3]  Francesc D. Muñoz-Escoí,et al.  A Protocol for Reconciling Recovery and High-Availability in Replicated Databases , 2006, ISCIS.

[4]  Hendrik Decker,et al.  k-bound GSI: a flexible database replication protocol , 2007, SAC '07.

[5]  Bettina Kemme,et al.  Postgres-R(SI): combining replica control with concurrency control based on snapshot isolation , 2005, 21st International Conference on Data Engineering (ICDE'05).

[6]  Sam Toueg,et al.  A Modular Approach to Fault-Tolerant Broadcasts and Related Problems , 1994 .

[7]  JoAnne Holliday.  Replicated database recovery using multicast communication , 2001, Proceedings IEEE International Symposium on Network Computing and Applications. NCA 2001.

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

[9]  Francisco Castro-Company,et al.  MADIS: A Slim Middleware for Database Replication , 2005, Euro-Par.

[10]  Ricardo Jiménez-Peris,et al.  Middleware based data replication providing snapshot isolation , 2005, SIGMOD '05.

[11]  Idit Keidar,et al.  Group communication specifications: a comprehensive study , 2001, CSUR.

[12]  Fernando Pedone,et al.  Database replication using generalized snapshot isolation , 2005, 24th IEEE Symposium on Reliable Distributed Systems (SRDS'05).

[13]  Gustavo Alonso,et al.  Exploiting atomic broadcast in replicated databases , 1997 .

[14]  Dimitrios Gunopulos,et al.  Indexing Multidimensional Time-Series , 2004, The VLDB Journal.

[15]  Roy Friedman,et al.  Strong and weak virtual synchrony in Horus , 1996, Proceedings 15th Symposium on Reliable Distributed Systems.

[16]  Kenneth Salem,et al.  Lazy database replication with snapshot isolation , 2006, VLDB.

[17]  Gustavo Alonso,et al.  MIDDLE-R: Consistent database replication at the middleware level , 2005, TOCS.

[18]  Gustavo Alonso,et al.  Don't Be Lazy, Be Consistent: Postgres-R, A New Way to Implement Database Replication , 2000, VLDB.

[19]  G. G. Stokes.  "J." , 1890, The New Yale Book of Quotations.

[20]  Alberto Bartoli,et al.  Online reconfiguration in replicated databases based on group communication , 2001, 2001 International Conference on Dependable Systems and Networks.

[21]  J. R. Garitagoitia,et al.  Non-blocking ROWA Protocols Implement GSI Using SI Replicas , 2007 .

[22]  Gustavo Alonso,et al.  Non-intrusive, parallel recovery of replicated data , 2002, 21st IEEE Symposium on Reliable Distributed Systems, 2002. Proceedings..

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

[24]  Luis Irún-Briz,et al.  Managing Transaction Conflicts in Middleware-based Database Replication Architectures , 2006, 2006 25th IEEE Symposium on Reliable Distributed Systems (SRDS'06).

[25]  Gustavo Alonso,et al.  Exploiting Atomic Broadcast in Replicated Databases (Extended Abstract) , 1997, Euro-Par.