<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><br>
On 02/09/2015 03:43 AM, Remy Dernat wrote:<br>
</div>
<blockquote cite="mid:54D87316.5030803@univ-montp2.fr" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">Le 09/02/2015 03:56, Christopher
Samuel a écrit :<br>
</div>
<blockquote cite="mid:54D821C8.8050406@unimelb.edu.au" type="cite">
<pre wrap="">On 07/02/15 14:57, Alan Louis Scheinine wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Only problem I've seen is that if a user allocates too much memory,
OOM killer can kill maintenance processes such as a scheduler daemon.
</pre>
</blockquote>
<pre wrap="">This is why we disable overcommit. :-)
</pre>
</blockquote>
<small>Hi,<br>
<br>
I already saw that problem on our master. The scheduler, SGE,
runs out of memory and OOM decided to kill it:</small><br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<span style="color: rgb(74, 85, 113); font-family: Verdana,
Geneva, Arial, Helvetica, sans-serif; font-size: 12px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: auto;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important;
float: none; background-color: rgb(255, 255, 255);">Dec 1
15:01:07 cluster1 kernel: Out of memory: Kill process 7963
(sge_qmaster) score 948 or sacrifice child<br>
<big><br>
<font color="#000000">I resolved that issue by disabling
"schedd_job_info" in SGE with "qconf -msconf".<br>
<br>
However, this setting gives significant informations about
our jobs.<br>
<br>
How should I adjust OOM killer ? Sould I set </font></big></span><br>
<span style="color: rgb(74, 85, 113); font-family: Verdana,
Geneva, Arial, Helvetica, sans-serif; font-size: 12px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: auto;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important;
float: none; background-color: rgb(255, 255, 255);"><big><font
color="#000000">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
</font></big></span>
<pre style="margin: 0px 0px 10px; padding: 5px; border: 0px; font-size: 13.6960000991821px; vertical-align: baseline; font-family: Consolas, Menlo, Monaco, 'Lucida Console', 'Liberation Mono', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Courier New', monospace, serif; overflow: auto; width: auto; max-height: 600px; word-wrap: normal; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 17.8048000335693px; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background: rgb(238, 238, 238);"><code style="margin: 0px; padding: 0px; border: 0px; font-size: 13.6960000991821px; vertical-align: baseline; font-family: Consolas, Menlo, Monaco, 'Lucida Console', 'Liberation Mono', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Courier New', monospace, serif; white-space: inherit; background: rgb(238, 238, 238);">vm.overcomm!
it_memory
= 2<small>
</small></code></pre>
<small>?<br>
<br>
</small><br>
</blockquote>
<br>
To be clear setting vm.overcommit_memory doesn't directly affect the
behavior of the OOM killer. Turning off overcommit prevents the
Linux virtual memory system from making promises it can't always
keep, which reduces/eliminates the need for the OOM Killer. <br>
<br>
Setting vm.overcommit_memory = 2 turns off overcommitting and is the
best choice if you want to avoid the OOM Killer. <br>
<br>
--<br>
Prentice<br>
<br>
</body>
</html>