Details
-
Bug
-
Resolution: Done
-
Major - P3
-
2.8.0-rc2
-
Fully Compatible
-
ALL
-
Description
Concurrent mapReduce operations that specify the same replacement collection can fail with "target namespace exists" errors when using WiredTiger. The same error is seemingly not reproducible with mmapv1.
I wouldn't expect a mapReduce operation with a 'replace' action to fail due to an existing namespace.
Error message:
Error: map reduce failed:{
|
"errmsg" : "exception: rename failed: { ok: 0.0, errmsg: \"target namespace exists\" }",
|
"code" : 10076,
|
"ok" : 0
|
}
|
Version: b766e395167dc27
Attachments
Issue Links
- depends on
-
SERVER-16507 initial sync needs to lock properly before truncating oplog
-
- Closed
-