[slurm-users] Replacement for FastSchedule since 19.05.3

Taras Shapovalov taras.shapovalov at brightcomputing.com
Wed Nov 6 08:16:37 UTC 2019

Hi Chris,

Thanks for the answer.
Does this mean that there is no way to get rid of annoying error messages
in the logs if we need the hardware autodetection (FastSchedule=0)?

error: FastSchedule will be removed in 20.02, as will the
FastSchedule=0 functionality. Please consider removing this from your
configuration now.

The error message suggests to "consider" this somehow. But I don't get how
we should consider this.

Best regards,


On Wed, Nov 6, 2019 at 5:30 AM Chris Samuel <chris at csamuel.org> wrote:

> On 5/11/19 6:36 am, Taras Shapovalov wrote:
> > Since Slurm 19.05.3 we get an error message that FastSchedule is
> > deprecated. But I cannot find in the documentation what is an
> > alternative option for FastSchedule=0. Do you know how we can do that
> > without using the option since 19.05.3?
> There isn't an alternative for FastSchedule=0 from what I can see, it
> seems that it doesn't work properly with cons_tres (which will be
> replacing cons_res) and so is destined for the scrap heap.
> See slide 10 of Tim's presentation from this years Slurm Users Group
> meeting:
> https://slurm.schedmd.com/SLUG19/Slurm_20.02_and_Beyond.pdf
> All the best,
> Chris
> --
>   Chris Samuel  :  http://www.csamuel.org/  :  Berkeley, CA, USA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20191106/7b64fb47/attachment-0001.htm>

More information about the slurm-users mailing list