[SERVER-53291] Add support for using larger distros with generated fuzzer tasks Created: 08/Dec/20 Updated: 29/Oct/23 Resolved: 10/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Richard Samuels (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-evgconfig | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | STM 2021-05-17 | ||||||||
| Participants: | |||||||||
| Story Points: | 1 | ||||||||
| Description |
|
One of the resharding fuzzer tests we'd like to enable in Evergreen would be a 6-shard, 2-node replica set shard, sharded cluster. With --storageEngineCacheSizeGB=1 this is more mongod processes than can be expected to safely run on a -small distro with 7.5GB of RAM. I'd want evergreen_gen_fuzzer_tests.py to support an use_large_distro: "true"-like option for all the build variants which currently run the resharding_fuzzer_inplace task so I can use large instance sizes for specific fuzzer tasks. |
| Comments |
| Comment by Githook User [ 10/May/21 ] |
|
Author: {'name': 'Richard Samuels', 'email': 'richard.l.samuels@gmail.com', 'username': 'richardsamuels'}Message: |
| Comment by Robert Guo (Inactive) [ 10/Dec/20 ] |
|
Yeah sounds good. I'll reassign to STM. |
| Comment by David Bradford (Inactive) [ 10/Dec/20 ] |
|
robert.guo Is this work that STM would like to do to ensure the team know how fuzzer tasks are being generated? I'd be happy to walk through the changes needed and review it. |