[torqueusers] Limit max jobs submitted
lloyd_brown at byu.edu
Tue Nov 22 14:38:02 MST 2011
There is a subtle but significant difference between the different
MAXJOB is a moab parameter that specifies how many jobs it will pay
attention to from it's resource manager (torque, in this case).
What we're talking about are torque parameters that can limit the number
of queued jobs either on a per-queue basis, or a per-user, per-queue basis.
For example, if you never want to allow any user to queue more than 1000
jobs, you can do something like this:
qmgr -c 'set queue batch max_user_queueable = 1000'
Now, I don't know how job arrays would interact with this (especially
given the discrepancy between torque arrays and moab arrays), but with
traditional jobs, when they have 1000 or more enqueued total (no matter
the state), qsub will refuse to queue any more for that user.
Sorry that wasn't clear earlier.
Fulton Supercomputing Lab
Brigham Young University
On 11/22/2011 02:28 PM, Andrus, Brian Contractor wrote:
> They do work, but they do not do what I need.
> See when someone submits >100000 array jobs, it fills up the job list that is used to schedule the jobs.
> That is MAXJOB tells how many jobs to work with within moab to decide priority and who to run. So if MAXJOB is set to 50000, and someone submits an array of 100000, then 1/2 of their jobs get pulled in and the rest are ignored (for now) by moab.
> Now along comes supersensitive.user who submits his interactive job, which will sit for way too long because moab isn't even going to schedule it. In fact, moab is ignoring it.
> I could set MAXJOB to 500000, but that still doesn't prevent a user from submitting too many jobs such that the list that is looked at does not over-fill.
> Is there a setting were if someone were to submit >X jobs (array or otherwise), torque/moab will not even allow it in?
> Brian Andrus
> ITACS/Research Computing
> Naval Postgraduate School
> Monterey, California
> voice: 831-656-6238
More information about the torqueusers