Hi Reuti,
Thank you for the fast answer.
Unifying them isn't really an option. They have different runtime and
overall slot limits.
When I try to configure the queues the way you say it, I get the
following message at the second queue:
denied: adding "B.q" to the subordinate_list of "A.q" would create a
loop in the slotwise preemption configuration!
But first tests indicate, that configuring one the queues is sufficient.
So thank you very much. I'll run some more tests, but right now I'm
happy with this solution.
Regards, Bastian
On 04/17/2012 06:37 PM, Reuti wrote:
Hi,
Am 17.04.2012 um 17:52 schrieb Bastian Kronenbitter:
I have one question concerning slotwise preemtion on mutliple queues.
Right now, we have installed multiple queues with different limits and resource
quotas, all running on the same nodes.
Now I would like to add another queue, which is subordinate to all of them.
Slotwise preemtion is working fine for each single queue instance, but not for
the sum of all.
For instance, with A.q and B.q being equally important queues, both configured
with
subordinate_list slots=4(sub.q:0:sr).
So with a setup like this:
job-ID prior name user state submit/start at queue
slots ja-task-ID
-----------------------------------------------------------------------------------------------------------------
150429 0.56000 Sleeper kronenbitter r 04/17/2012 17:39:15
[email protected] 1
150430 0.56000 Sleeper kronenbitter r 04/17/2012 17:39:15
[email protected] 1
150431 0.56000 Sleeper kronenbitter r 04/17/2012 17:39:30
[email protected] 1
150432 0.56000 Sleeper kronenbitter r 04/17/2012 17:39:30
[email protected] 1
150433 0.55200 Sleeper kronenbitter r 04/17/2012 17:39:45
[email protected] 1
I would like one of the jobs in sub.q being suspended. But it is only as soon
as either A.q or B.q runs 4 jobs.
Is it possible to take into account the sum of the jobs running in A.q and B.q?
I'm sorry if the answer is obvious or already given in another email, I could
not find it.
What's different between A.q and B.q, any option to unify them?
What about:
In A.q:
subordinate_list slots=4(B.q:1, sub.q:2:sr)
In B.q:
subordinate_list slots=4(A.q:1, sub.q:2:sr)
I assume you limit queues A.q,B.q hosts {*} to slots=4 already. Hence, A.q plus
B.q will never cross 4 and jobs in sub.q should be suspended first. So A.q and
B.q can't suspend each other essentially.
-- Reuti
Thanks in advance,
Bastian Kronenbitter
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users