-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
v3.2
-
Repl 2016-10-10
-
(copied to CRM)
This is to avoid the syncing node winding up with an incomplete set of data due to the inability of initial sync to properly handle renameCollection. See SERVER-4941 for more details.
- is duplicated by
-
SERVER-25040 Initial syncing node maintains tmp collection from map reduce when primary has renamed it
- Closed
- is related to
-
SERVER-4941 collection rename may not replicate / clone properly during initial sync
- Closed
-
SERVER-29772 Provide option to 3.2 and 3.4 to allow initial sync to complete even when it encounters renameCollection entries
- Closed