-
Type: Bug
-
Resolution: Gone away
-
Priority: Trivial - P5
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
ALL
-
25
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.
- related to
-
SERVER-26867 Timeout-related assert.soon failures should trigger the hang analyzer
- Closed