Three-phase commit protocol: Difference between revisions

Content deleted Content added
Extensions: Corrected the link to the publication
Be clearer in introduction that 3pc guarantees a "commit or abort" (not just commit), and clarify that the improvement it makes over 2pc is to eliminate the indefinite blocking edge case.
Line 1:
{{Short description|Distributed algorithm}}
In [[computer networking]] and distributed [[database]]s, the '''three-phase commit protocol''' ('''3PC''')<ref name=3PC>{{cite tech report
| last = Skeen
| first = Dale
Line 7:
| institution = Department of Computer Science, Cornell University
| url = https://ecommons.cornell.edu/handle/1813/6323
}}</ref> is a [[distributed algorithm]] whichthat letsensures all nodes in a [[distributed system|system]] agree to [[Commit (data management)|commit]] or abort a [[database transaction|transaction]]. It isimproves a more failure-resilient refinement ofupon the [[two-phase commit protocol]] (2PC) by eliminating the possibility of indefinite blocking caused by a failure during the commit phase.
 
==Motivation==