-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
None
-
Fully Compatible
-
ALL
-
v3.6
-
Repl 2017-12-18, Repl 2018-01-01
We put in a back-door here so that we could unittest timestamps. It says that non-master-slave, non-replicated applyOps writes are timestamped with their provided timestamps. This means that standalone applyOps writes will get timestamped with the provided timestamps. If the provided timestamps are out of order (which is almost certain), that will cause a problem.