-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
Replication
If we encounter a collection in fetchAndInsertMissingDoc with a UUID that is unrecognized in the UUIDCatalog, it should be tracked in a missingUUIDs set so that it can be accounted for once the corresponding oplog application drop/rename operation for that collection is reached. At the end of oplog application, we should assert that this missingUUIDs set is empty and all missing UUIDs have been accounted for.