Re: [slurm-users] Replacement for FastSchedule since 19.05.3

2019-11-05 Thread Chris Samuel
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

Re: [slurm-users] job priority keeping resources from being used?

2019-11-05 Thread c b
On Sun, Nov 3, 2019 at 7:18 AM Juergen Salk wrote: > > Hi, > > maybe I missed it, but what does squeue say in the reason field for > your pending jobs that you expect to slip in? > > the reason on these jobs is just "Priority". > Is your partition maybe configured for exclusive node access,

Re: [slurm-users] Help with preemtion based on licenses

2019-11-05 Thread Mark Hahn
The limiting factor in our cluster is licenses and I want to have high and low priority jobs where submitting a high priority job will preempt (suspend) a low priority job if all the licenses are already in use. But what are you expecting to happen? that Slurm will somehow release the

[slurm-users] Replacement for FastSchedule since 19.05.3

2019-11-05 Thread Taras Shapovalov
Hey guys, 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? Best regards, Taras

Re: [slurm-users] Help with preemtion based on licenses

2019-11-05 Thread Oytun Peksel
Hi, Apparently the original email got lost here so here it is. If anyone has any idea how to this please comment. On Thursday, June 20, 2019 at 3:20:41 AM UTC+2, Eric Wittmayer wrote: Hi Slurm experts, I'm new to SLURM and could really use some help getting preemption working. The limiting

Re: [slurm-users] Running job using our serial queue

2019-11-05 Thread David Baker
Hello, Thank you for your replies. I double checked that the "task" in, for example, taskplugin=task/affinity is optional. In this respect it is good to know that we have the correct cgroups setup. So in theory users should only disturb themselves, however in reality we find that there is