Bill, Jobs submitted with a -t time option that exceeds the partition's MaxTime will remain in the pending state. The idea is to keep the job queued until evening or weekend hours when the partition's time limit may be extended.
A different approach was used for jobs that exceed a qos's MaxWall time - the submissions fails with a message to the user that a size or time limit was exceeded. Don From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, July 27, 2011 2:18 PM To: [email protected] Subject: [slurm-dev] srun -t option I working on a problem related to enforcement of a MaxSubmit limit for a QOS. While doing some investigation I saw the following statement in the srun man documentation regarding the '-t' option: -t, --time=<time> Set a limit on the total run time of the job or job step. If the requested time limit for a job exceeds the partition's time limit, the job will be left in a PENDING state (possibly indefi- nitely). I suspect there may be some correlation between what is being seen as the MaxSubmit limit being exceeded and jobs that have been submitted with '-t' values larger than the QOS limit. The user checked the number of jobs submitted with an 'sacct' command and if there aren't accounting record yet for these PENDING jobs they wouldn't be seen using this command I have tried unsuccessfully to reproduce this situation because I can't get the jobs to be left in the PENDING state. Can anyone please tell me under what conditions the job will be left in the PENDING state rather than being cancelled? Best Regards, Bill
