On Extending the Primary-copy Database Replication Paradigm

In database replication, primary-copy systems sort out easily the problem of keeping replicate data consistent by allowing only updates at the primary copy. While this kind of systems are very efficient with workloads dominated by read-only transactions, the update-everywhere approach is more suitable for heavy update loads. However, it behaves worse when dealing with workloads dominated by read-only transactions. We propose a new database replication paradigm, halfway between primary-copy and update-everywhere approaches, which permits improving system performance by adapting its configuration to the workload, by means of a deterministic database replication protocol which ensures that broadcast writesets are always going to be committed.

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

[2]  Sam Toueg,et al.  Inconsistency and contamination (preliminary version) , 1991, PODC '91.

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

[4]  Francesc D. Muñoz-Escoí,et al.  A Recovery Protocol for Middleware Replicated Databases Providing GSI , 2007, The Second International Conference on Availability, Reliability and Security (ARES'07).

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

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

[7]  Gustavo Alonso,et al.  Using Optimistic Atomic Broadcast in Transaction Processing Systems , 2003, IEEE Trans. Knowl. Data Eng..

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

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

[10]  Fernando Pedone,et al.  Conflict-aware load-balancing techniques for database replication , 2008, SAC '08.

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

[12]  Gustavo Alonso,et al.  Extending DBMSs with satellite databases , 2008, The VLDB Journal.

[13]  GrayJim,et al.  A critique of ANSI SQL isolation levels , 1995 .

[14]  Christian A. Plattner.  Ganymed: A Platform for Database Replication , 2006 .

[15]  Kenneth P. Birman,et al.  Exploiting virtual synchrony in distributed systems , 1987, SOSP '87.

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

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

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

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

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

[21]  Francesc D. Muñoz-Escoí,et al.  Optimizing Certification-Based Database Recovery , 2007, Sixth International Symposium on Parallel and Distributed Computing (ISPDC'07).

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