[SERVER-43251] Investigate whether mapReduce tests can be used in stepdown suites Created: 10/Sep/19  Updated: 29/Oct/23  Resolved: 19/Dec/19

Status: Closed
Project: Core Server
Component/s: MapReduce, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.3.3

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Ted Tuckman
Resolution: Fixed Votes: 0
Labels: qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-42680 M/R Agg: Generate full pipeline from ... Closed
Related
related to SERVER-43303 Re introduce mapReduce fsm tests in s... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2019-12-16, Query 2019-12-30
Participants:

 Description   

Many of these tests were blacklisted because of the possibility of a std::terminate during a stepdown. I'm not sure what caused this in the first place but it seems likely we will resolve this after translating the mapReduce implementation to aggregation.

This ticket tracks the work to figure out whether these tests can be un-blacklisted (have the 'does_not_support_stepdown' tag removed). It'd be great if we could figure out what was causing this originally but it doesn't seem as high priority.



 Comments   
Comment by Githook User [ 19/Dec/19 ]

Author:

{'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}

Message: SERVER-43251 Fix up map reduce blacklists
Branch: master
https://github.com/mongodb/mongo/commit/6adf8ad187352b0b253d4fbb282c8af9d1e89f18

Comment by Nicholas Zolnierz [ 14/Oct/19 ]

As part of SERVER-43303, we will likely explicitly blacklist the mapReduce FSM tests from the concurrency stepdown suites to avoid the error in the description. Hopefully as part of this ticket we can remove that restriction as well.

Comment by Charlie Swanson [ 12/Sep/19 ]

If we find out that they can (which I suspect and hope), there's some code such as this which should be deleted.

Generated at Thu Feb 08 05:02:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.