When we apply single-phase createIndexes oplog entries during oplog application, there are certain index creation errors that are safe to ignore (based on assumptions about the current state of the database and future oplog entries to apply). However, our optimization for the empty collection case has a slightly different exclusion list from the non-empty collection case.
We should resolve this inconsistency as this may have implications for initial sync and tenant migration use cases.
- is related to
-
SERVER-72618 Untimestamped writes to the catalog can occur when dropping unfinished indexes during replication rollback
-
- Closed
-
- related to
-
-
- Backlog
-
-
SERVER-73874 clean up geo_small_large.js and initial_sync_index_conflict.js
-
- Closed
-