Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Execution Team 2020-06-29
Description
Multiple tests in replication_recovery_test.cpp check for which order the oplog applier applies them. When using a storage engine that does not support document-level locking the ordering is guaranteed because all jobs get scheduled on the same replication writer thread because the '_id' field is not used when dispatching the jobs. See this code:
We should fix these tests so they don't assume this order.