[SERVER-75632] Enable lockCodeSegmentsInMemory in config fuzzer suites Created: 03/Apr/23  Updated: 21/Jun/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Jason Chan Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-73943 Pin code pages in memory in memory co... Closed
Assigned Teams:
Service Arch
Sprint: Service Arch 2023-04-17, Service Arch 2023-05-01, Service Arch 2023-06-12
Participants:

 Description   

Currently, we don't run lockCodeSegmentsInMemory because certain build variants do not have the proper ulimits set. Once set, we should enable the fuzzing.



 Comments   
Comment by Jason Chan [ 21/Jun/23 ]

Sending this to backlog since I think this currently has low-value in terms of test coverage, and we should reconsider doing this once SERVER-73943 is confirmed to be working in the field. The complexity in this ticket is making sure current and future variants that run the config fuzzer suites have ulimits configured to allow enough memory to be pinned on startup.

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