about.
The workable option I can think of right now is to have everyone run their
jobs with --exclusive as an extra argument.
On Thu, Apr 30, 2020 at 12:22 PM Rutger Vos wrote:
> This seems like the easiest solution, but how would that interact with MPI
> jobs? Apologies if these are r
o 1 CPU.
>
>
>
> *Doug Meyer*
>
>
>
> *From:* slurm-users *On Behalf Of
> *Rutger Vos
> *Sent:* Wednesday, April 29, 2020 1:20 PM
> *To:* Slurm User Community List
> *Subject:* [External] Re: [slurm-users] one job at a time - how to set?
>
>
>
> Hi Mic
node definition in slurm.conf for that one node to 1 CPU.
>>
>>
>>
>> *Doug Meyer*
>>
>>
>>
>> *From:* slurm-users *On Behalf
>> Of *Rutger Vos
>> *Sent:* Wednesday, April 29, 2020 1:20 PM
>> *To:* Slurm User Community List
el or something?
Thanks again!
Rutger
On Wed, Apr 29, 2020 at 10:06 PM Renfro, Michael wrote:
> That’s a *really* old version, but
> https://slurm.schedmd.com/archive/slurm-15.08.13/sbatch.html indicates
> there’s an exclusive flag you can set.
>
> On Apr 29, 2020,
Hi,
for a smallish machine that has been having degraded performance we want to
implement a policy where only one job (submitted with sbatch) is allowed to
run and any others submitted after it are supposed to wait in line.
I assumed this was straightforward but I can't seem to figure it out. Can
