mapReduce with a sharded output collection assigns the UUID obtained from the config server to the final output collection. mapReduce "replace" will drop the existing output collection, which has the same UUID as the new output collection. Two-phase-drop may cause the dropCollection to finish after the renameCollection finishes, erroneously removing the UUIDCatalog entry for the output collection.
- is duplicated by
-
SERVER-33599 Out collection not in UUID catalog when shards started as replica sets in mapReduce_outSharded.js, mrShardedOutput.js, forget_mr_temp_ns.js
- Closed
-
SERVER-35425 After a map reduce an exception NamespaceNotFound happens in a secondary shard
- Closed
- related to
-
SERVER-34539 Re-enable sharded mapReduce concurrency testing and only use a single mongos
- Closed