[SERVER-80253] Run fewer pipelines per timeseries fuzzer task, but more tasks Created: 18/Aug/23  Updated: 29/Oct/23  Resolved: 15/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Charlie Swanson Assignee: Charlie Swanson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-76600 Increase timeouts for aggregation_tim... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.1
Participants:
Linked BF Score: 126

 Description   

It looks like we solved part of the problem in SERVER-76600, but there is still a problem where a single individual fuzzer generated test file can take more than 30 minutes. I think we should allow an hour per test.



 Comments   
Comment by Githook User [ 15/Sep/23 ]

Author:

{'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}

Message: SERVER-80253 Run fewer timeseries pipelines per task
Branch: master
https://github.com/mongodb/mongo/commit/aa9591382b6aa55687284ae6bded66495ee6a0f4

Comment by Charlie Swanson [ 25/Aug/23 ]

Update again: still having trouble with that approach and it's kinda tricky to debug. Going to have to dig deeper on the evergreen integration between server and jstestfuzz controlling the options like how many pipelines to run.

Comment by Charlie Swanson [ 23/Aug/23 ]

Update here: I'm trying a patch to both bump the idle timeout and also decrease the number of pipelines generated to see if either/both of them are valid options here.

 

https://spruce.mongodb.com/version/64e6521bd6d80a45e609cbd2/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

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