[torqueusers] Job eligible, nodes free, but job would not start

Garrick Staples garrick at clusterresources.com
Fri Oct 13 12:50:41 MDT 2006

On Fri, Oct 13, 2006 at 12:43:00PM -0400, Neelesh Arora alleged:
> An update:
> I notice that when these jobs are stuck, one way to get them started is 
> to set a walltime (using qalter) less than the default walltime. We set 
> a default_walltime of 9999:00:00 at the server level and require the 
> users to specify the needed cpu-time.
> This was set a long time ago and has not been causing any issues. But it 
> seems now that if you have set this default and then a user submits a 
> job with an explicit -l walltime=<time> specification, then that job 
> runs while older jobs with default walltime wait.
> Can some one please shed some light on this - I am out of clues here?

Walltime is really important to maui.  Smaller walltimes allow jobs to
run within backfill windows.  If everyone has infinite walltimes, you
basicly reduce yourself to a simple FIFO scheduler and might as well
just use pbs_sched.

More information about the torqueusers mailing list