operationTime
Parent: Causal Consistency · Published reference · snapshot 2026-10-15
↓ Facts as markdownall context files
Depth-first rabbithole dossier for operationTime; source-anchored research pack.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Facts and statements
- [low] The server reports the operationTime whether the operation succeeded or not, and drivers must save the operationTime in the ClientSession regardless of the operation's success status. Sources: https://raw.githubusercontent.com/mongodb/specifications/master/source/causal-consistency/causal-consistency.md [source]
- [high] Drivers track the operationTime of the last operation in a session, and each message from a data node in a causally consistent session receives the operationTime, which is the last known logical time persisted in the oplog on that node. Sources: http://muratbuffalo.blogspot.com/2024/04/implementation-of-cluster-wide-logical.html, https://dev.to/franckpachot/read-your-writes-on-replicas-postgresql-wait-for-lsn-and-mongodb-causal-consistency-4he2 [source]
Children
- No children recorded.