<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Modify it and raise the priority to something very, very high.</p>
    <p>scontrol update job=JOBID priority=9999999</p>
    <p>Brian Andrus<br>
    </p>
    <div class="moz-cite-prefix">On 9/16/2021 8:39 AM, 顏文 wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAEx9ML6VbLFUQrMueJRSTiGwRaVDaOawRvT6QD9vDVUo5L69Cw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Dear users
        <div><br>
        </div>
        <div>Thank for the immediate replies.I currently have one
          important job running. How to prevent the running job from
          being preempted? That job has been running for two weeks, and
          I am afraid it will be terminated in the next few days. Can we
          do anything to secure the job from being cancelled and
          preempted? Thanks.</div>
        <div><br>
        </div>
        <div>regards,</div>
        <div>Peter</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">Russell Jones <<a
            href="mailto:arjones85@gmail.com" moz-do-not-send="true">arjones85@gmail.com</a>>
          於 2021年9月14日 週二 下午10:52寫道:<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 dir="ltr">The other option is creating a "special"
            partition that only this user(s) can submit to, where
            jobs running in that partition have a higher priority than
            all the others (if you are using partition priority like we
            are).<br>
          </div>
          <br>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Tue, Sep 14, 2021 at
              3:26 AM Loris Bennett <<a
                href="mailto:loris.bennett@fu-berlin.de" target="_blank"
                moz-do-not-send="true">loris.bennett@fu-berlin.de</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">Dear Peter,<br>
              <br>
              顏文 <<a href="mailto:peteryen2017@gmail.com"
                target="_blank" moz-do-not-send="true">peteryen2017@gmail.com</a>>
              writes:<br>
              <br>
              > Dear Mr. Zillner<br>
              ><br>
              > I would like the specific running job not being
              rescheduled , but also can not be terminated or cancelled
              in any way. If the job is cancelled, I need to start it
              over again. Normally this kind of jobs require weeks to<br>
              > finish. So the time costs it take to restart is quite
              significant. Can your suggestions also achieve that?
              Thanks.<br>
              <br>
              I have not tried this, but could you define a QOS which
              cannot be<br>
              preempted by the other QOSs?  That way you can also
              restrict access to<br>
              the QOS, since a non-preemptable QOS will probably be more
              attractive<br>
              than a preemptable one.  You would then obviously have to
              explain to the<br>
              users which QOS they should use.<br>
              <br>
              Cheers,<br>
              <br>
              Loris<br>
              <br>
              > with regards,<br>
              > Peter<br>
              ><br>
              > Florian Zillner <<a
                href="mailto:fzillner@lenovo.com" target="_blank"
                moz-do-not-send="true">fzillner@lenovo.com</a>> 於
              2021年9月14日 週二 下午3:40寫道:<br>
              ><br>
              >  See the no-requeue option for SBATCH:<br>
              ><br>
              >  --no-requeue<br>
              >  Specifies that the batch job should never be
              requeued under any circumstances. Setting this option will
              prevent system administrators from being able to restart
              the job (for example, after a scheduled<br>
              >  downtime), recover from a node failure, or be
              requeued upon preemption by a higher priority job. When a
              job is requeued, the batch script is initiated from its
              beginning. Also see the --requeue option. The<br>
              >  JobRequeue configuration parameter controls the
              default behavior on the cluster. <br>
              ><br>
              >  <a href="https://slurm.schedmd.com/sbatch.html"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://slurm.schedmd.com/sbatch.html</a><br>
              ><br>
              >  Get Outlook for Android<br>
              >
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
              >  From: slurm-users <<a
                href="mailto:slurm-users-bounces@lists.schedmd.com"
                target="_blank" moz-do-not-send="true">slurm-users-bounces@lists.schedmd.com</a>>
              on behalf of 顏文 <<a
                href="mailto:peteryen2017@gmail.com" target="_blank"
                moz-do-not-send="true">peteryen2017@gmail.com</a>><br>
              >  Sent: Tuesday, September 14, 2021 7:02:13 AM<br>
              >  To: <a href="mailto:slurm-users@lists.schedmd.com"
                target="_blank" moz-do-not-send="true">slurm-users@lists.schedmd.com</a>
              <<a href="mailto:slurm-users@lists.schedmd.com"
                target="_blank" moz-do-not-send="true">slurm-users@lists.schedmd.com</a>><br>
              >  Subject: [External] [slurm-users] How can I do to
              prevent a specific job from being prempted? <br>
              >   <br>
              >  Dear slurm users, <br>
              ><br>
              >  I have some specific jobs that can't be terminated,
              otherwise they need to be rerun from the beginning. Can we
              simply apply some settings (either by user or
              administrator) so that these jobs will not be<br>
              >  preempted ? Thanks.<br>
              ><br>
              >  with regards,<br>
              >  Peter<br>
              <br>
            </blockquote>
          </div>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>