[SERVER-34539] Re-enable sharded mapReduce concurrency testing and only use a single mongos Created: 18/Apr/18  Updated: 06/Dec/22  Resolved: 09/Mar/20

Status: Closed
Project: Core Server
Component/s: MapReduce, Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: tig-concurrency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-43303 Re introduce mapReduce fsm tests in s... Closed
Related
is related to SERVER-20057 Concurrent, sharded mapReduces can fa... Closed
is related to SERVER-33538 mapReduce "replace" on a sharded outp... Closed
Assigned Teams:
Sharding
Participants:
Story Points: 2

 Description   

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.



 Comments   
Comment by Max Hirschhorn [ 02/May/19 ]

I don't believe SERVER-37679 is a reason not to do this ticket because the existing map_reduce*.js FSM workloads don't use sharded=true.

Comment by Maria van Keulen [ 18/Apr/18 ]

max.hirschhorn yes I think that would be sufficient.

Comment by Max Hirschhorn [ 18/Apr/18 ]

maria.vankeulen, are you asking that we add a version of the concurrency_sharded.yml test suite that uses a single mongos process?

Generated at Thu Feb 08 04:37:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.