Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

DevProd Correctness
Confidence Status:
None
Work Order:
3
Size Category:
TBD
CAR Domain/s:
None

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

https://spruce.mongodb.com/version/687a8cc694411200076bec99/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC is an example of resmoke_jobs being too high for a few specific sharding tests, causing reproducible OOMs with the changes in https://github.com/10gen/mongo/pull/38149 (minus hardcoding the number of jobs to a very low number, which I'll revert before merging). resmoke_jobs should be chosen in such a way that we saturate the evergreen host, but without OOMing.

is related to

SERVER-52987 Complete TODO listed in SERVER-37165

Closed

SERVER-97562 Revisit the number of Resmoke jobs running per host on Evg

Closed

SERVER-101493 Make burn_in respect resmoke_job_max for the underlying task

Needs Scheduling

SERVER-101494 Allow tests to set lower resmoke_job_factors individually in burn_in

Needs Scheduling

Assignee:: Unassigned
Reporter:: Brad Cater
Participants:: Brad Cater
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jul 22 2025 09:18:50 PM UTC
Updated:: Jul 23 2025 12:11:26 AM UTC