Sean Brisbane writes:
> Does anyone have a feeling for why setting a high Priority on a partition
> makes jobs run in that partition first regardless that a job in a different
> Partition may have a much higher overall priority?
Perhaps because that is what it was designed to do? Did you try us
Are you uising the prioirty/multifactor plugin? What are the values of the
various Priority* weight factors?
On Tue, Mar 12, 2019 at 12:42 PM Sean Brisbane
wrote:
> Hi,
>
> Thanks for your help.
>
> Either setting qos or setting priority doesn't work for me. However I
> have found the cause if
Hi,
Thanks for your help.
Either setting qos or setting priority doesn't work for me. However I have
found the cause if not the reason.
Using a Priority setting on the partition called "Priority" in slurm.conf
seems to force all jobs waiting on this queue to run first regardless of
any qos set
Sean Brisbane writes:
> I'm trying to troubleshoot why the highest priority job is not next to run,
> jobs in the partition called "Priority" seem to run first.
>
[...]
> The partition called "Priority" has a priority boost assigned through qos.
>
> PartitionName=Priority Nodes=compute[01-02] De
Hi,
I'm looking to have a way an administrator can boost any job to be next to
run when resources become available. What is the best practice way to do
this? Happy to try something new :-D
The way I thought to do this was to have a qos with a large priority and
manually assign this to the job.
