<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I might look at these options:</p>
<dl compact="compact">
<dt><b>preempt_reorder_count=#</b></dt>
<dd>
Specify how many attempts should be made in reording preemptable
jobs to
minimize the count of jobs preempted.
The default value is 1. High values may adversely impact
performance.
The logic to support this option is only available in the
select/cons_res and
select/cons_tres plugins.
</dd>
<dt><b>preempt_strict_order</b></dt>
<dd>
If set, then execute extra logic in an attempt to preempt only
the lowest
priority jobs.
It may be desirable to set this configuration parameter when
there are multiple
priorities of preemptable jobs.
The logic to support this option is only available in the
select/cons_res and
select/cons_tres plugins.
</dd>
<dt><b>preempt_youngest_first</b></dt>
<dd>
If set, then the preemption sorting algorithm will be changed to
sort by the
job start times to favor preempting younger jobs over older.
(Requires
preempt/partition_prio or preempt/qos plugins.)
</dd>
</dl>
<p>In general slurm will try not to preempt if it can avoid it.
These options can help to guide that a bit more intelligently.</p>
<p>-Paul Edmon-<br>
</p>
<div class="moz-cite-prefix">On 5/29/19 8:53 AM, Mike Harvey wrote:<br>
</div>
<blockquote type="cite"
cite="mid:16ff0485-7906-840f-21e8-e87c0a76c18f@bucknell.edu">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">I am relatively
new to SLURM, and am having difficulty configuring our
scheduling to behave as we'd like.</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Partition based
job preemption is configured as follows:<br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">PreemptType=preempt/partition_prio<br>
PreemptMode=suspend,gang<br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">This has been
working fine. However, we recently added an older server to
the cluster, and tried to give it a higher weight than our
other servers, with the intent that it would only used when
resources on other lower-weighted nodes are unavailable. What
seems to happen, though, is that a newly submitted job will
preempt/suspend a lower-priority job on a lower-weighted node
before running on the higher-weighted node. What we would like
is for preemption to only occur when no resources are
available.</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Is this
possible?</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Thanks,</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Mike Harvey</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Systems
Administrator</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Bucknell
University</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><a
href="mailto:harvey@bucknell.edu" moz-do-not-send="true">harvey@bucknell.edu</a></div>
</div>
</blockquote>
</body>
</html>