Three-Phase Commit

A distributed transaction protocol in which nodes agree to commit an update through three phases: prepare, pre-commit, and commit.

1 articleLast mentioned

Three-Phase Commit (3PC) is an atomic commit protocol by which several nodes in a distributed system agree either to commit a transaction everywhere or to abort it everywhere. A coordinator first asks each node whether it is prepared, then announces that the transaction will be committed, and finally instructs the nodes to commit. It was proposed by Dale Skeen in 1981.

The pre-commit phase was added to reduce the blocking problem of Two-Phase Commit (2PC), in which participants can wait indefinitely if the coordinator fails. However, every transaction requires several rounds of synchronous communication with all participants, so latency is high and the cost of agreement grows with the number of nodes. Because it cannot guarantee safety under network partitions, consensus algorithms such as Paxos and Raft are more widely used in practice.

This entry is based on AIPOST articles and widely known facts. If something is wrong, please send us a correction request.

Articles covering this entry

  • Pando: The Git Backend OpenAI Built for a 2,442% Surge in CommitsAI News ·

    â–² Three-Phase Commit and Write-Ahead Log bottlenecks

    Read article

Found a mistake or missing an entry?

Wiki entries are based on AIPOST articles and widely known facts. If an entry is wrong, send us a correction request and we will check and fix it. Names from new articles are added to the wiki after the article is published.