Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: MapReduce, Sharding
Labels:
- tig-concurrency

Assigned Teams:

Sharding
Story Points:
2
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: [DO NOT USE] Backlog - Sharding Team
Reporter:: Maria van Keulen
Participants:: [DO NOT USE] Backlog - Sharding Team, Maria van Keulen, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Apr 18 2018 03:48:58 PM UTC
Updated:: Dec 06 2022 03:32:00 AM UTC
Resolved:: Mar 09 2020 08:33:15 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates