Excellent question thank you.
Each queue has the following for queue sorting:
$ qconf -sq bio | grep seq
seq_no 100
$ qconf -sq free64 | grep seq
seq_no 7000
So it should pick queue bio first. What I think is happening is that
if a task first lands on free64 because bio queue was full, it picks up
"h_rt" wallclock limit and if that task is then restarted and lands on
bio queue which has no "h_rt", the original "h_rt" from free64
sticks. If this is true then I would think this is a bug?
Joseph
On 05/29/2015 11:30 AM, Feng Zhang wrote:
A question: for "-q free64,bio", what GE does to choose an available
queue for a job? Will it sort and do alphabetical order?
On Fri, May 29, 2015 at 8:12 AM, William Hay <[email protected]> wrote:
On Thu, 28 May 2015 19:27:07 +0000
Joseph Farran <[email protected]> wrote:
Hi all.
I am not sure if this is a bug or the way Grid Engine works.
We have several queues our users submit jobs to. One of the queues
"free64" has a 3-day wall-clock limit:
$ qconf -sq free64 | grep "_rt"
s_rt 72:00:00
h_rt 72:05:00
While other queue "bio" does not:
$ qconf -sq bio | grep "_rt"
s_rt INFINITY
h_rt INFINITY
When a user submits a job to both queues "-q free64,bio", jobs that
run longer than 3 days are killed whether they land on "free64" or
"bio" queue. Why are jobs that land on the "bio" queue being
killed after 3 days?
Are you sure the whole job is in the bio queue? Might a slave task be
in the free64 queue?
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
