-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
None
-
Fully Compatible
-
ALL
-
v4.4, v4.2, v4.0
-
20
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.