-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
-
ALL
-
16
In MapReduce, incremental collections are cloned in initial sync even though they are created with setReplicatedWrites(false). This appears to be the only place this is an issue, though we should make sure there are no other places where this should be handled.
- is depended on by
-
SERVER-35498 Unblacklist mapReduce tests from the initial sync dynamic passthrough
- Closed
- is related to
-
SERVER-35365 MapReduce temporary inc collections should be written to the local database
- Closed
- related to
-
SERVER-33638 CheckReplDBHash should ignore mapreduce incremental collections
- Closed
-
SERVER-27206 blacklist tests involving MapReduce from initial sync dynamic passthroughs
- Closed
-
SERVER-42554 Complete TODO listed in SERVER-27147
- Closed
-
SERVER-43460 Complete TODO listed in SERVER-27147
- Closed
-
SERVER-26965 Use RAII type for turning off replicated writes
- Closed
-
SERVER-31216 Mark internal collections in metadata so tools don't dump them
- Closed