-
Type:
Task
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:
-
Backwards Compatibility:Fully Compatible
-
Backport Requested:v3.2
-
Epic Link:
-
Sprint:Repl 2016-10-10
-
Case:
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 documented by
-
DOCS-10763 Document that upgrading to 3.2.12 and 3.4.0 may cause initial sync to fail if collection renames are happening
-
- Closed
-
- 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
-