[Moabusers] MAXJOB and MAXPROC change ?
Chris Samuel
csamuel at vpac.org
Wed Mar 28 22:44:36 MDT 2007
Hi folks,
We've got an interesting situation, we have:
USERCFG[DEFAULT] MAXJOB=20:25
USERCFG[DEFAULT] MAXPROC=90
USERCFG[DEFAULT] MAXIJOB=5
So we want no user to be able to have more than 20/25 jobs running and never
any more than 90 CPUs over that number of jobs (to balance between the
parametric users and the large parallel users). Nobody can have more than 5
jobs eligible to run (again because of the parametric users who could
inadvertently do queue stuffing).
It's worked in the past, but we've noticed now that under 5.0.0p3 and the
current 5.1.0rc2 snapshot that we have a user now running over 50 single CPU
jobs and with 5 idle jobs and heaps of blocked jobs (and no free CPUs).
If I lower MAXPROC to 50 then his idle jobs become blocked because he's
exceeded the MAXPROC limit, but MAXJOB doesn't seem to having any effect!
Help!
cheers,
Chris
--
Christopher Samuel - (03)9925 4751 - VPAC Deputy Systems Manager
Victorian Partnership for Advanced Computing http://www.vpac.org/
Bldg 91, 110 Victoria Street, Carlton South, VIC 3053, Australia
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/moabusers/attachments/20070329/bad3a2c8/attachment.bin
More information about the moabusers
mailing list