[torqueusers] torque does not kill jobs when wall_time or cpu_time reached
glen.beane at gmail.com
Fri Jun 4 05:12:12 MDT 2010
On Fri, Jun 4, 2010 at 4:45 AM, Arnau Bria <arnaubria at pic.es> wrote:
> I found why jobs are not killed when cput/wall_time is reached.
> # qstat -f 10626859|grep Resource_List
> Resource_List.neednodes = 1
> Resource_List.nodect = 1
> Resource_List.nodes = 1
> there's no default resource time limits.
> Resource_List.cput or Resource_List.walltime
> So I assume that my resource_max default values are not taken in consideration:
> resources_max.cput = 01:30:00
> resources_max.walltime = 03:00:00
> and that "breaks" what man says:
> The maximum amount of each resource which can be requested by a single job in this queue. The queue value supersedes any server wide maximum limit. For-
> mat: "resources_max.resource_name=value", see qmgr(1B); default value: infinite usage.
> The list of default resource values which are set as limits for a job residing in this queue and for which the job did not specify a limit. Format:
> "resources_default.resource_name=value", see qmgr(1B); default value: none; if not set, the default limit for a job is determined by the first of the fol-
> lowing attributes which is set: server’s resources_default, queue’s resources_max, server’s resources_max. If none of these are set, the job will unlimited
> resource usage.
please fill out a TORQUE bug report at www.clusterresources.com/bugzilla
More information about the torqueusers