-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
-
45
This ticket is to track the idemponecy failures we found in BF's after reducing the initial sync attempts to 1 in SERVER-31093.
- depends on
-
SERVER-7515 idempotence violation when intermediate document exceeds size threshold
- Open
-
SERVER-27357 Recreating collection with different collation during collection cloning phase can causes initial sync attempt to fail
- Backlog
-
SERVER-32225 Initial sync should ignore multiple text indexes on same collection error
- Closed
-
SERVER-32903 Ambiguous field name error should be ignored during initial sync
- Closed
-
SERVER-33956 A sequence of rename and create collections that do not arrive at the correct end state
- Closed
-
SERVER-44462 Run listIndexes with a single snapshot during initial sync
- Closed
-
SERVER-33060 Increase initial sync attempts in initial sync passthrough
- Closed
-
SERVER-27122 Restart initial sync for known index idempotency errors; fail for unknown ones.
- Backlog