From Slack Thread:

It looks like the hang analyzer taking core dumps is filling up 100GB in https://jira.mongodb.org/browse/BF-36363. From the system logs in https://parsley.mongodb.com/evergreen/mongodb_mongo_master_enterprise_amazon_linux2_ar[…]_16_41_34/0/system?bookmarks=0,15107&filters=100mongod%2520, I see the total virtual memory used by all 24 mongod processes is 99GB. The resident memory is less than 5GB. I feel like one avenue would be to investigate what allocated memory within the mongod process because the WT cache is still restricted to 1GB. This is maybe better performed by the Server team so I'll tag
@Abdul Qadeer
as well