Integrity Dangers in Certification-Based Replication Protocols

Database replication protocols check read-write and/or write-write conflicts. If there are none, protocols propagate transactions to the database, assuming they will eventually commit. But commitment may fail due to integrity constraints violations. Also, the read actions of integrity checking may give raise to new conflicts. Thus, some more care must be taken if, in addition to the consistency of transactions and replicas, also the consistency of integrity constraints is to be maintained. In this paper, we investigate how certification-based replication protocols can be adapted to correctly and transparently deal with the built-in integrity support provided by the underlying DBMS. Also, we experimentally demonstrate the negative effects that an incorrect management of integrity constraints causes in a database replication distributed system.

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

[2]  André Schiper,et al.  Comparison of database replication techniques based on total order broadcast , 2005, IEEE Transactions on Knowledge and Data Engineering.

[3]  Miron Livny,et al.  Conflict detection tradeoffs for replicated data , 1991, TODS.

[4]  Gilles M. E. Lafue.  Semantic Integrity Dependencies and Delayed Integrity Checking , 1982, VLDB.

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

[6]  Michael S. Okun,et al.  Atomic writes for data integrity and consistency in shared storage devices for clusters , 2002 .

[7]  Hendrik Decker,et al.  Integrity Checking and Maintenance in Relational and Deductive Database and Beyond , 2007 .

[8]  Brian Randell,et al.  Operating Systems, An Advanced Course , 1978 .

[9]  Luis Irún-Briz,et al.  Managing Multiple Isolation Levels in Middleware Database Replication Protocols , 2006, ISPA.

[10]  Luís Veiga,et al.  RepWeb: replicated Web with referential integrity , 2003, SAC '03.

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

[12]  Francesc D. Muñoz-Escoí,et al.  Extending Middleware Protocols for Database Replication with Integrity Support , 2008, OTM Conferences.

[13]  Stephanie J. Cammarata,et al.  Extending a relational database with deferred referential integrity checking and intelligent joins , 1989, SIGMOD '89.

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

[15]  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).

[16]  Stephen Gilmore,et al.  Flexible Skeletal Programming with eSkel , 2005, Euro-Par.

[17]  Dennis Shasha,et al.  Making snapshot isolation serializable , 2005, TODS.

[18]  François Llirbat,et al.  Using Versions in Update Transactions: Application to Integrity Checking , 1997, VLDB.

[19]  R. Salinas,et al.  SIRC, a multiple isolation level protocol for middleware-based data replication , 2007, 2007 22nd international symposium on computer and information sciences.

[20]  H. Decker,et al.  On Supporting Integrity Constraints in Relational Database Replication Protocols , 2008 .

[21]  Gustavo Alonso,et al.  A new approach to developing and implementing eager database replication protocols , 2000, TODS.

[22]  Amnon Barak,et al.  Atomic writes for data integrity and consistency in shared storage devices for clusters , 2002, Fifth International Conference on Algorithms and Architectures for Parallel Processing, 2002. Proceedings..

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

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

[25]  Fernando Pedone,et al.  Tashkent: uniting durability with transaction ordering for high-performance scalable database replication , 2006, EuroSys.

[26]  Dennis Shasha,et al.  The dangers of replication and a solution , 1996, SIGMOD '96.