Bug 129156 - OOM killer terminating apps while there's still free memory
Summary: OOM killer terminating apps while there's still free memory
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
(Show other bugs)
Version: 3.0
Hardware: x86_64 Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-04 15:40 UTC by Joshua Baker-LePain
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-04 19:17:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Memory graph created by Ganglia (11.26 KB, image/gif)
2004-08-04 15:41 UTC, Joshua Baker-LePain
no flags Details
CPU graph created by Ganglia. (10.66 KB, image/gif)
2004-08-04 15:42 UTC, Joshua Baker-LePain
no flags Details

Description Joshua Baker-LePain 2004-08-04 15:40:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115

Description of problem:
I have several compute nodes with 6GB of RAM and 2GB of swap, running
primarily ls-dyna, a commercial FEM code compiled for AMD64.  On one
of these, a simulation was actively running with a VSS of 
2274180 and a RSZ of 652240 (almost a quarter of it is swapped out!).
 Another user tried to fire up a simulation that wanted 3371384 of
VSS.    The OOM killer swiftly terminated it.  Should that happen? 
Any way to make it not happen?

Version-Release number of selected component (if applicable):
kernel-2.4.21-9.0.3.ELsmp

How reproducible:
Didn't try


Additional info:

I've set /proc/sys/vm/inactive_clean_percent to 30 in response to bug
115438 and /proc/sys/vm/pagecache to "1 15 15" in response to bug 118152.

Comment 1 Joshua Baker-LePain 2004-08-04 15:41:01 UTC
Created attachment 102419 [details]
Memory graph created by Ganglia

Comment 2 Joshua Baker-LePain 2004-08-04 15:42:15 UTC
Created attachment 102420 [details]
CPU graph created by Ganglia.

Comment 3 Joshua Baker-LePain 2004-08-04 19:17:25 UTC
Upon further investigation, there may have been enough memory pressure
on the system to trigger OOM after all.  I'm going to close this,
since I can't be completely clear on what happened.  Sorry for the noise.


Note You need to log in before you can comment on or make changes to this bug.