[SERVER-44739] Running gdb concurrently with testing can starve the box of memory Created: 19/Nov/19 Updated: 27/Oct/23 Resolved: 06/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Trivial - P5 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Robert Guo (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 25 | ||||||||||||
| Description |
|
One example of a test box has 7GB of RAM (and I assume is not configured with swap). Running the hang analyzer against a mongod can consume multiple GBs of memory. In one case, three GDBs were simultaneously being run consuming 2GB, 1.4GB and 1.67GBs. This resulted in memory pressure that caused allocations from within a mongod process to fail. |
| Comments |
| Comment by Robert Guo (Inactive) [ 06/Apr/21 ] |
|
I'm going to close this ticket since it doesn't look like OOM issues have been happening frequently after we switched the EC2 instance type from c to m, effectively doubling the available memory per resmoke job. Feel free to reopen if this is still a concern |
| Comment by Brooke Miller [ 16/Jun/20 ] |
|
Leaving this ticket in the Backlog until this failure re-occurs. |