Pool priority overrides

Deadline
1

Hi, we just switched from priority_pool_date to pool_priority_date job queuing. It looks good, but the best would be to if we could override this on a per job level. For example if there is a low priority job with a pool that is first place on 3 machines, those machines start the job anyway. Even if there are more important jobs. If I could mark that job to use priority_pool_date order, so use machines only if there are no higher priority jobs in the repository. The default would be pool_priority_date for any jobs, just with an option (use with responsibility :slight_smile: to change that. Is there a way currently to do this or similar?

Thanks,
Gabor

2

Could you just create a “low_priority” pool and assign it with low priority to some machines, and then submit these low priority jobs to that pool? They would work the same as you described, as they would only get picked up when the higher priority jobs have been processed.

Cheers,

  • Ryan