-
Type: Improvement
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: Replication
-
Minor Change
-
RPL 1 04/03/15, RPL 3 05/15/15
https://groups.google.com/forum/#!topic/mongodb-user/PeJxfoH6RF4
{w: 3, j: true}should wait for journaling on all waited nodes, in order to permit safe two-phase commit systems, and other high-resilience clients, to be sure that data has actually hit the disk on those replicas. This also seems like the natural behavior for this combination of options: w says how many replicas to wait for, and j says to wait for journalling on those nodes.
- is duplicated by
-
SERVER-6998 Write concern cannot guarantee journal write on secondaries
- Closed
- is related to
-
SERVER-18023 Don't await commit when applying logops in initial sync
- Closed
- related to
-
SERVER-7156 w:majority issues with votes
- Closed
-
SERVER-17852 Reduce unnecessary replicated journal write concern flag for multi-update/delete
- Closed