Revision as of 09:49, 25 July 2023 edit Citation bot (talk \| contribs) Bots 5,865,512 edits Misc citation tidying. \| Use this bot. Report bugs. \| #UCB_CommandLine ← Previous edit		Revision as of 07:24, 16 January 2024 edit undo David Eppstein (talk \| contribs) Autopatrolled, Administrators 235,639 edits Idit Keidar Next edit →
Line 19: ==Extensions== Using Skeen's original three-phase commit protocol, it is possible that a quorum becomes connected without being able to make progress (this is not a deadlock situation; the system will still progress if the network partitioning is resolved). Keidar and Dolev's E3PC<ref name=E3PC>{{cite journal\|last=Keidar\|first=Idit\|author1-link=Idit Keidar\|author2=Danny Dolev \|title=Increasing the Resilience of Distributed and Replicated Database Systems\|journal= Journal of Computer and System Sciences\|volume=57\|issue=3\|date=December 1998\|pages=309–324\| url=http://webee.technion.ac.il/~idish/Abstracts/jcss.html\|doi=10.1006/jcss.1998.1566\|doi-access=free}}</ref> refines Skeen's three-phase commit protocol and solves this problem in a way which ''always'' allows a quorum to make progress.

Three-phase commit protocol: Difference between revisions