Atomic Commit in Distributed Database Systems: The Approaches of Blocking and Non-Blocking Protocols

Loading...
Thumbnail Image
Date
2014-10
Journal Title
Journal ISSN
Volume Title
Publisher
International Journal of Engineering Research & Technology
Abstract
In distributed database systems, the primary need for commit protocols is to maintain the atomicity of distributed transactions. Atomic commitment issue is of prime importance in the distributed system and the issue becomes more necessary to deal with if some of the sites participating in the execution of the transaction commitment fail. Several atomic commit protocols have evolved to terminate distributed transactions. This paper presents an overview of a distributed transaction model, and a description of the two phase commit (2PC) protocol (which is blocking) and the one phase (1PC) commit protocols (which is non-blocking). This paper further examines the assumptions of these commit protocols in their bid to addressing the atomic commitment issue in distributed database systems. By restricting possible encountered failure to site failure, drawbacks in the assumptions of these atomic commit protocols were identified, which clearly show that the nonblocking protocol studied addresses the drawbacks of the widely used blocking protocol, 2PC, but in itself is no messiah (as it also constitutes drawbacks in practice). This work will spur other researchers to a more vigorous reconsideration of the 1PC nonblocking protocol.
Description
Keywords
Atomic commit protocols, Blocking, Distributed Database Systems, Stable database
Citation