DISTRIBUTED RELIABILITY
PROTOCOL
Kirti
08BCE133
INTRODUCTION
Distributed reliability protocols aim
1. to maintain atomicity
2. to maintain durability
of distributed transactions that execute over a
number of databases.
Most problematic issues in a distributed
transaction are commit, termination, and
recovery.
Distributed reliability protocols
Commit protocols
How to execute a commit command for distributed transactions
How to ensure atomicity ?
Termination protocols
If a failure occurs at a site, how can the other operational sites
deal with it
Non-blocking: the occurrence of failures should not force the
sites to wait until the failure is repaired to terminate the
transaction
Recovery protocols
When a failure occurs, how do the sites where the failure
occurred deal with it
Independent: a failed site can determine the outcome of a
transaction without having to obtain remote information
Coordinator: The process at the site where the
transaction originates and which controls the
execution
Participant: The process at the other sites that
participate in executing the transaction
2-Phase Commit Protocol
Very simple protocol that ensures the atomic
commitment of distributed transactions.
It insists that all sites involved in the
execution of a distributed transaction agree
to commit the transaction before its effects
are made permanent.
Phase 1: The coordinator gets the
participants ready to write the results into the
database
Phase 2: Everybody writes the results into the
database
Centralized 2-PC communication
structure
2-PC Protocol actions
Global Commit Rule
– The coordinator aborts a transaction if and
only if at least one participant votes to
abort it
– The coordinator commits a transaction if and
only if all of the participants vote to
commit it
Thank You