-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Catalog, Index Maintenance, Replication
-
None
-
ALL
-
Execution Team 2019-12-02, Execution Team 2019-12-16
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Without this we can get idempotency problems during initial sync. We can try to create two indexes during collection cloning that never existed simultaneously in real life. Eventually we will get a dropIndex oplog entry for one of the two, but at collection clone time we don't know which one so we can't just drop one to fix the idempotency violation.
This was hypothesized while I talked with milkie regarding SERVER-27122.
- is depended on by
-
SERVER-33946 Decrease number of initial sync attempts in tests to 1
-
- Blocked
-
- is related to
-
SERVER-27122 Restart initial sync for known index idempotency errors; fail for unknown ones.
-
- Backlog
-