Managing Transaction Conflicts in Middleware-based Database Replication Architectures

Database replication protocols need to detect, block or abort part of conflicting transactions. A possible solution is to check their writesets (and also their readsets in case a serialisable isolation level is requested), which however burdens the consumption of CPU time. This gets even worse when...

Full description

Saved in:
Bibliographic Details
Main Authors: Munoz-Escoi, F.D., Pla-Civera, J., Ruiz-fuertes, M. I., Irun-Briz, L., Decker, H., Armendariz-inigo, J.E., Gonzalez De Mendivil, J.R.
Format: Conference Proceeding
Language:English
Subjects:
Abortion
Concurrency control
Data structures
Delay systems
Maintenance
Middleware
Multicast protocols
Testing
Transaction databases
Online Access:Request full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Database replication protocols need to detect, block or abort part of conflicting transactions. A possible solution is to check their writesets (and also their readsets in case a serialisable isolation level is requested), which however burdens the consumption of CPU time. This gets even worse when the replication support is provided by a middleware, since there is no direct DBMS support in that layer. We propose and discuss the use of the concurrency control support of the local DBMS for detecting conflicts between local transactions and writesets of remote transactions. This allows to simplify many database replication protocols and to enhance their performance
ISSN:1060-9857
2575-8462
DOI:10.1109/SRDS.2006.29