<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Just curious as to expectations out here.</p>
<p>When <i>should </i>slurm immediately reject a job?</p>
<p>Brian Andrus<br>
</p>
<div class="moz-cite-prefix">On 2/8/2022 11:41 PM, Alexander Block
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:cc460966-c35f-d2a2-b1b4-d7a14729f2f0@lrz.de">Hi Mike,
<br>
<br>
I'm just discussing a familiar case with SchedMD right now (ticket
13309). But it seems that it is not possible with Slurm to submit
jobs that request features/configuration that are not available at
the moment of submission.
<br>
<br>
Cheers,
<br>
<br>
Alexander
<br>
<br>
<br>
Am 08.02.2022 um 23:26 schrieb <a class="moz-txt-link-abbreviated" href="mailto:z148x@arcor.de">z148x@arcor.de</a>:
<br>
<blockquote type="cite">Dear all,
<br>
<br>
sbatch jobs are immediately rejected if no suitable node is
available in
<br>
the configuration.
<br>
<br>
<br>
sbatch: error: Memory specification can not be satisfied
<br>
sbatch: error: Batch job submission failed: Requested node
configuration
<br>
is not available
<br>
<br>
These jobs should be accepted, if a suitable node will be active
soon.
<br>
For example, these jobs could be in PartitionConfig.
<br>
<br>
Is that configurable?
<br>
<br>
<br>
Many thanks,
<br>
<br>
Mike
<br>
<br>
</blockquote>
<br>
</blockquote>
</body>
</html>