-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Querying, Replication
-
None
-
Fully Compatible
-
Quint Iteration 3, Quint Iteration 4, Quint Iteration 5, Quint Iteration 6, Quint Iteration 7, QuInt 8 08/28/15
Writes in MongoDB replica sets are "committed" when the majority of voting nodes in the replica set confirm the write (n.b., arbiters cannot confirm writes). This ticket is to add a feature to query-like operations (find, count, aggregate, etc) to restrict the data observed to data known to have been committed at the replica set level. It is an approximate but imperfect analog of "w: majority" writes.
In MongoDB deployments using an MVCC storage engine, such as WiredTiger, this behavior could be implemented by having the replication subsystem retain the newest "known committed" version of data on each node, and have the query system serve "committed" reads from that version rather than the newest version.
- depends on
-
SERVER-18999 FindCommand should ignore $-prefixed fields it doesn't know about
- Closed
- is depended on by
-
JAVA-2002 Support ReadConcern
- Closed
-
SERVER-18995 Support reading $readMajorityTemporaryName from command metadata
- Closed
- is related to
-
DRIVERS-254 Add support for the readConcern option.
- Closed
- related to
-
SERVER-42343 WiredTigerLAS.wt grows when lagged node is in maintenance mode
- Closed
-
SERVER-20146 Support readConcern in shell helper db.collection.find()
- Closed