presumed-commit · shipping · also Presumed commit protocol, Presumed-commit two-phase commit

Presumed commit

Presumed commit is a two-phase commit optimization in which a recovery coordinator with no retained protocol state answers an inquiring prepared participant with commit.

Related Observatory article: Read on hesela.com

In basic R* presumed commit, a nonleaf force-writes a collecting record naming its immediate subordinates before sending PREPARE. Updating participants still force their prepare records before voting yes. The optimization does not remove preparation logging. [1]

A collecting record with no later protocol record means the process was still collecting, not prepared. Recovery aborts that transaction, waits for acknowledgements and logs completion before forgetting it. A nonroot that subsequently logged prepare instead asks its parent for the outcome. [1]

On the successful update path, the root coordinator still forces its commit decision. Participants can log commit without forcing it and omit commit acknowledgements. Abort recovery instead retains the outcome until the required recipients acknowledge it; this trades early participant-list persistence for less successful-commit traffic. [2]

The answer must come from the responsible recovery coordinator. A participant timeout is not permission to commit. R* remains blocking when the required coordinator cannot be contacted. [1]

When R* mixes presumed abort and presumed commit, protocol identity accompanies PREPARE, the first protocol log record and recovery inquiries. The same absence of state cannot be interpreted without that identity. [1]

Relations

related
Two-phase commit, Presumed abort

Limitations

  • Read-only leaves can avoid logging, but R* nonleaves with entirely read-only subtrees still write a forced collecting record and an unforced commit record. [1]
  • Fewer messages do not imply universally lower latency: the extra early forced write and workload mix matter. Presumed-either is a later, distinct protocol that conditionally exploits participant records already made durable. [2]

Citations

  1. Mohan, Lindsay and Obermarck. Transaction Management in the R* Distributed Database Management System. TODS 11(4), 1986, sections 4-5 and footnote 8. (accessed 2026-11-16)
  2. Attaluri and Salem. The Presumed-Either Two-Phase Commit Protocol. IEEE TKDE 14(5), 2002, pp. 1190-1191, sections 2-3. (accessed 2026-11-16)
Sources & caveats
  • Primary-source synthesis of historical commit protocols, independently source-reviewed. No distributed recovery experiment or performance measurement was executed.
  • Operational inference: establish protocol identity and intact recovery history before interpreting absence. Accidental deletion or loss of the coordinator log is not the protocol's legitimate no-information case.

JSON: /data/terms/presumed-commit.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Presumed commit. Hesela. 2026-11-16. https://hesela.dev/terms/presumed-commit/