-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
Labels:
-
Backwards Compatibility:Fully Compatible
-
Backport Completed:
-
Epic Link:
-
Sprint:Repl 10 (02/19/16)
-
Linked BF Score:0
Once the OpTime is updated then progress can be reported and used upstream, or locally for replication.
- is depended on by
-
SERVER-26416 Cannot read own write after drop with read/write concern "majority" with inMemory storage engine
-
- Closed
-
-
SERVER-23770 Remove read_concern_majority_passthrough_WT on Enterprise RHEL 6.2 (inMemory) on 3.2 branch
-
- Closed
-
- is related to
-
SERVER-22276 implement "j" flag in write concern apply to secondary as well as primary
-
- Closed
-
-
SERVER-22575 Make periodic write flushing a service of the storage system
-
- Closed
-
- related to
-
SERVER-22533 Enable ReadConcern.Majority tests without journaling
-
- Closed
-