I had seen the bit preempting and assumed that just by marking a job as
production, its guaranteed whatever resources are allocated to it (by the
job config) and non-producton jobs could be de-prioritized to meet the
requirements.
It makes sense now.
Thanks for the quick response, as always.
On
This is, unfortunately, only sparsely documented [1]:
Whether or not this is a production task backed by quota (Default: False).
> Production jobs may preempt any non-production job, and may only be
> preempted by production jobs in the same role and of higher priority. To
> run jobs at this level
I have a pretty basic job
prod_resources = Resources(cpu = 0.5, ram = 256*MB, disk=2000*MB)
My cluster has 3 slaves, each with 4 cpu cores and 16GB or RAM but I'me
getting
Job creation failed due to error:
Insufficient resource quota: CPU quota exceeded by 1.00 core(s); RAM quota
exceeded by 512
