-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Sharding
-
2
Concurrent sharded mapReduce testing was disabled as part of SERVER-20057. However, it appears the bug in this ticket only occurs when there are multiple mongoses. I believe this testing should be re-enabled, but only use one mongos, since there may be other concurrent sharded mapReduce related issues, such as SERVER-33538, that can be found from this test coverage.
- duplicates
-
SERVER-43303 Re introduce mapReduce fsm tests in sharded suites
- Closed
- is related to
-
SERVER-20057 Concurrent, sharded mapReduces can fail when temporary namespaces collide across mongos processes
- Closed
-
SERVER-33538 mapReduce "replace" on a sharded output collection can lead to UUIDCatalog inconsistencies
- Closed