Distributed Transaction Management
Transaction management in distributed database systems
Distributed transaction management deals with the problems of always providing a consistent distributed database in the presence of a large number of transactions (local and global) and failures (communication link and/or site failures). This is accomplished through (i) distributed commit protocols that guarantee atomicity property; (ii) distributed concurrency control techniques to ensure consistency and isolation properties; and (iii) distributed recovery methods to preserve consistency and durability when failures occur.
A transaction is a sequence of actions on a database that forms a basic unit of reliable and consistent computing, and satisfies the ACID property. In a distributed database system (DDBS), transactions may be local or global. In local transactions, the actions access and update data in a single site only, and hence it is straightforward to ensure the ACID property....
- 1.Alsberg P, Day JD. A principle for resilient sharing of distributed resources. In: Proceedings of the 2nd International Conference on Software Engineering; 1976. p. 562–70.Google Scholar
- 2.Badal DZ. Correctness of concurrency control and implications for distributed databases. In: Proceedings of the 3rd Computer Software and Applications Conference; 1979. p. 588–94.Google Scholar
- 3.Balter R, Berard P, Decitre P. Why control of the concurrency level in distributed systems is more fundamental than deadlock management. In: Proceedings of the ACM SIGACT-SIGOPS 1st Symposium on the Principles of Distributed Computing; 1982. p. 183–93.Google Scholar
- 5.Bernstein PA, Hadzilacos V, Goodman N. Concurrency control and recovery in database systems. Boston: Addison-Wesley; 1987.Google Scholar
- 7.Chrysanthis PK, Samaras G, Al-Houmaily YJ. Recovery and performance of atomic commit processing in distributed database systems, Chapter 13. In: Kumar V, Hsu M, editors. Recovery mechanisms in database systems. Upper Saddle River: Prentice-Hall; 1998.Google Scholar
- 9.Hadzilacos T, Yannakakis M. Deleting completed transactions. In: Proceedings of the 5th ACM SIGACT-SIGMOD Symposium on Principles of Database Systems; 1986. p. 43–6.Google Scholar
- 10.Lampson B, Sturgis H. Crash recovery in a distributed data storage system. Technical report, Computer Science Laboratory, Xerox Palo Alto Research Center, 1976.Google Scholar
- 12.Shapiro R, Millstein R. Reliability and fault recovery in distributed processing. In: Oceans ’77 Conference Record: Third Annual Combined Conference; 1977. p. 425–29.Google Scholar
- 13.Skeen D. Non-blocking commit protocols. In: Proceedings of the ACM SIGMOD International Conference on Management of Data. p. 133–42.Google Scholar
- 14.Stonebraker M, Neuhold EJ. A distributed database version of ingres. In: Proceedings of the 2nd Berkeley Workshop on Distributed Data Management and Computer Networks; 1977. p. 19–36.Google Scholar
- 15.The Tandem Performance Group. Tandem database group – nonstop sql: a distributed, high-performance, high-availability implementation of sql. In: Proceedings of the 2nd International Workshop on High Performance Transaction Systems; 1987. p. 60–104.Google Scholar