-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.4.3
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Repl 2021-01-25
-
16
Currently, as part of initial_sync_drop_against_last_stable.js, we drop a collection and then create a new one with the same name. We also insert a document into the new collection and check that it exists once initial sync is complete. Currently, there is a race that the document is not covered by initial sync (the optime for the insert is > than the stopOptime for initial sync), and we fail the assertion that the inserted document exists after initial sync is complete.