Hi Reed,
Reed Dier writes:
> On Jun 27, 2023, at 1:10 AM, Loris Bennett
> wrote:
>
> Hi Reed,
>
> Reed Dier writes:
>
> Is this an issue with the relative FIFO nature of the priority scheduling
> currently with all of the other factors disabled,
> or since my queue is fairly deep, is th
> On Jun 27, 2023, at 1:10 AM, Loris Bennett wrote:
>
> Hi Reed,
>
> Reed Dier mailto:reed.d...@focusvq.com>> writes:
>
>> Is this an issue with the relative FIFO nature of the priority scheduling
>> currently with all of the other factors disabled,
>> or since my queue is fairly deep, is this
Hi Reed,
Reed Dier writes:
> Hoping this will be an easy one for the community.
>
> The priority schema was recently reworked for our cluster, with only
> PriorityWeightQOS and PriorityWeightAge contributing to the priority
> value, while PriorityWeightAssoc, PriorityWeightFairshare,
> PriorityW
Reed,
You may want to look at the timelimit aspect of the job(s).
For one to 'squeeze in', it needs to be able to finish before the
resources in use are expected to become available.
Consider:
Job A is running on 2 nodes of a 3 node cluster. It will finish in 1 hour.
Pending job B will run fo
