Hi,
Am 12.05.2011 um 17:13 schrieb Chris Jewell:
Hi Reuti,
So, the problem showed up again.
Is the interactive queue interactive only? I mean, when the qtype
is only set to "batch" only interactive (better: immediate) jobs
should end there and it could be removed from the queue request and
the resource quota.
I had a problem with parallel jobs ending up in the wrong queue (ie
not respecting the interactive/batch config setting), so I set up a
JSV to explicitly set the queue type.
yeah, we had that too. But it showed up 3 to 4 times in a row and then
not again for weeks, So I never had a chance to investigate it in
detail.
Such strange behavior I saw up to now when you request some other
consumable like in your case h_vmem in combination with a resource
quota limit (is h_vmem consumable?).
$ qquota -u "*"
doesn't return anything?
$ qquota -u "*" returns correctly for one user who is currently
using 9 slots (we had a FS issue this morning, so our cluster is
currently quiet).
To reiterate, yes, h_vmem is consumable. To clear the problem, I
had to disable the resource quota (enable FALSE), let the job run,
and then re-enable. Also, this problem only seems to occur when
using parallel environments.
Is the quota still correct afterwards? Or do you face this in addition:
https://arc.liv.ac.uk/trac/SGE/ticket/1316
https://arc.liv.ac.uk/trac/SGE/ticket/817
-- Reuti
NB: Sent from my iBook.
Cheers,
Chris
--
Dr Chris Jewell
Department of Statistics
University of Warwick
Coventry
CV4 7AL
UK
Tel: +44 (0)24 7615 0778
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
