<div dir="ltr">Hi Paul, Marcus,<div><br></div><div>Thank you for your replies. Using partition priority all makes sense. I was thinking of doing something similar with a set of nodes purchased by another group. That is, having a private high priority partition and a lower priority "scavenger" partition for the public. In this case scavenger jobs will get killed when preempted. </div><div><br></div><div>In the present case , I did wonder if it would be possible to do something with just a single partition -- hence my question.Your replies have convinced me that two partitions will work -- with preemption leading to re-queued jobs. </div><div><br></div><div>Best regards,</div><div>David </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 15, 2019 at 3:09 PM Paul Edmon <<a href="mailto:pedmon@cfa.harvard.edu">pedmon@cfa.harvard.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Yup, PriorityTier is what we use to do exactly that here. That
said unless you turn on preemption jobs may still pend if there is
no space. We run with REQUEUE on which has worked well.</p>
<p><br>
</p>
<p>-Paul Edmon-</p>
<p><br>
</p>
<div class="gmail-m_8153567423438616633moz-cite-prefix">On 2/15/19 7:19 AM, Marcus Wagner
wrote:<br>
</div>
<blockquote type="cite">
Hi David,<br>
<br>
as far as I know, you can use the PriorityTier (partition
parameter) to achieve this. According to the manpages (if I
remember right) jobs from higher priority tier partitions have
precedence over jobs from lower priority tier partitions, without
taking the normal fairshare priority into consideration.<br>
<br>
Best<br>
Marcus<br>
<br>
<div class="gmail-m_8153567423438616633moz-cite-prefix">On 2/15/19 10:07 AM, David Baker
wrote:<br>
</div>
<blockquote type="cite">
<div id="gmail-m_8153567423438616633divtagdefaultwrapper" dir="ltr">
<p style="margin-top:0px;margin-bottom:0px">Hello.</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">We have a small set
of compute nodes owned by a group. The group has agreed that
the rest of the HPC community can use these nodes providing
that they (the owners) can always have priority access to
the nodes. The four nodes are well provisioned (1 TByte
memory each plus 2 GRID K2 graphics cards) and so there is
no need to worry about preemption. In fact I'm happy for the
nodes to be used as well as possible by all users. It's just
that jobs from the owners must take priority if resources
are scarce. </p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">What is the best way
to achieve the above in slurm? I'm planning to place the
nodes in their own partition. The node owners will have
priority access to the nodes in that partition, but will
have no advantage when submitting jobs to the public
resources. Does anyone please have any ideas how to deal
with this?</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">Best regards,</p>
<p style="margin-top:0px;margin-bottom:0px">David</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
</div>
</blockquote>
<br>
<pre class="gmail-m_8153567423438616633moz-signature" cols="72">--
Marcus Wagner, Dipl.-Inf.
IT Center
Abteilung: Systeme und Betrieb
RWTH Aachen University
Seffenter Weg 23
52074 Aachen
Tel: +49 241 80-24383
Fax: +49 241 80-624383
<a class="gmail-m_8153567423438616633moz-txt-link-abbreviated" href="mailto:wagner@itc.rwth-aachen.de" target="_blank">wagner@itc.rwth-aachen.de</a>
<a class="gmail-m_8153567423438616633moz-txt-link-abbreviated" href="http://www.itc.rwth-aachen.de" target="_blank">www.itc.rwth-aachen.de</a>
</pre>
</blockquote>
</div>
</blockquote></div>