-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v3.2
-
Repl 11 (03/11/16), Repl 12 (04/01/16)
-
0
Currently with the changes for the SERVER-22276 (and SERVER-22495) the committed snapshot is not correctly being updated based on the replica set config and journal write concern flag.
Rules to apply to correct the problem:
The meaning of the snapshot depends on the replica set config (“writeConcernMajorityJournalDefault”) which indicates if it is tied to the durable or applied optime.
Notable Exceptions (when both aren't true or false)
- Applied Snapshot OpTime, with J:True
- Wait for snapshot for writeOpTime (Applied)
- Wait for replication of durableOpTime >= writeOpTime (new code)
- Durable Snapshot OpTime, with J:False
- Do not wait for snapshot, and you cannot read your own write
- Wait for replication of majority optime (applied = normal)
- is depended on by
-
SERVER-23956 Inconsistent behavior between 3.2.6-rc0 and 3.3.5 for writeconcern majority and journaling
- Closed
-
SERVER-22533 Enable ReadConcern.Majority tests without journaling
- Closed
- is duplicated by
-
SERVER-22572 readConcern majority doesn't consider replica-set changes
- Closed
- is related to
-
SERVER-23365 Resolve ReadConcern passthrough failures
- Closed