"Loris Bennett" <[email protected]> writes: > We do already use weighting, but my understanding was that this would > only affect the order in which resources are assigned and not prevent a > job from starting even when resources are available. > > I assume that there is some valid reason for a job waiting, but it is > not apparent to me. I guess it would be helpful if it were possible to > see exactly what resources a job is waiting for, but I haven't come > across a way to do that.
The situation of jobs not starting despite resources being available has occurred again. - User A with the highest priority jobs has reached her running job limit, so no more of her jobs can start. Her jobs have a time limit of 2 days. - User B with the next highest priority jobs needs more memory than is available on the free node, so his job can't start there. His jobs have a time limit of 3 days. - User C is next in line and needs all the CPUs of the node, but very little memory. It seems that his job should start, but it doesn't. His jobs have a time limit of 3 days. Should User B's job prevent User C's job from starting? Or is it because User C's time limit is greater than that of User A? I can sort of see why a lower priority job with a long run-time maybe shouldn't start before a higher priority, short run-time job which is being held back due to the running job limit, but is this really what is going on? Regards Loris -- This signature is currently under construction.
