Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.0.20, 4.4.0-rc10, 4.2.9, 4.7.0
-
Component/s: Replication, Storage
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Backport Requested:v4.4, v4.2, v4.0
-
Linked BF Score:20
Description
When we do a timestamped write that may not be strictly ordered with respect to the oplog (that is, if it has a timestamp less than or equal to the latest optime in the oplog), we must set orderedCommit to false to ensure oplog visibility is updated. ReplicationConsistencyMarkers::setAppliedThrough does not do this.
It might make sense to do this in StorageInterfaceImpl::_updateWithQuery to catch any others.