David, Ronny,
We've confirmed that this behavior is happening in Maui. Moab Workload
Manager currently has the desired behavior with suspended jobs accruing
priority (and also correctly handles different classes involved). We
hope that over the next few weeks we will be able to make these
improvements in Maui as well. We will keep the list posted on our progress.
--
Joshua Butikofer
Cluster Resources, Inc.
[EMAIL PROTECTED]
(801) 798-7488
--------------------------
David Corredor wrote:
The problem is not just that the suspended job gets once again preempted
by a job of its same class from the IDLE queue, this happens regardless
of the class of the new job.
Ex. 3 queues (1 verylong, 1 long, 1 fast. Fast preempts long and
verylong, and long preempts verylong, verylong should not preempt).
- Submit 1 long job so that it takes all resources in cluster.
- Submit a verylong job so that it waits in the IDLE queue.
- Submit a fast job.
The fast job preempts the long one, and once it finishes, instead of the
long one to resume execution, the verylong kicks in and preempts it once
again (and it shouldn't).
<quote who="Ronny T. Lampert">
.....
However I experience the very same problem as you do (I need the
QUEUETIMEWEIGHT set to 1) - the preempted ones stay suspended and instead
a
NEW job from the batch queue is started :-(
I think this is a bug: suspended jobs *should age*, too.
Or automatically get a slightly higher priority than the highest in the
same
class to prevent it from staying suspended and interrupted by jobs from
the
same class.
Could some developer shortly comment on that issue?
Thanks!
Ronny
_______________________________________________
mauiusers mailing list
[email protected]
http://www.supercluster.org/mailman/listinfo/mauiusers
_______________________________________________
mauiusers mailing list
[email protected]
http://www.supercluster.org/mailman/listinfo/mauiusers
