[GE issues] [Issue 2943] New - Job groups for easier handling of jobs which belong together
reuti at staff.uni-marburg.de
Tue Mar 3 16:26:58 GMT 2009
Summary|Job groups for easier handling of jobs which belong to
------- Additional comments from reuti at sunsource.net Tue Mar 3 08:26:56 -0800 2009 -------
Having a bunch of jobs in the cluster, it's for now possible to kill them via wildcards "qdel Gaussian_CrO2*" (whether they are tied togehther by hold_jid or not). Sometimes you want to handle this
more easily by some kind of "@jobgroup".
$ qsub -cg @myjobgroup myjob # create a jobgroup @myjobgroup and submit job.
(Also called auto create group. When no job is left in the @jobgroup, the @jobgroup is removed automatically. Option "-cg auto" should create a random uniq jobgroup, maybe with option -
tersegroup to output the @jobgroup name only for batch processing.)
$ qsub -g @myjobgroup myjob # submit a job bound to a jobgroup.
(Will use an already existing jobgroup. Or maybe -gu for user's group, -gp for project's group)
$ qsub -gh @myjobgroup myjob # submit a job to a jobgroup and add all right now exsiting jobs in this @jobgroup to hold_jobid -"group hold")
(Will use an already existing jobgroup.)
$ qgsub @myjobgroup
(Will request a permanent job group [maybe tied to user/project/department]. - "Your jobgroup request @myjobgroup has been granted".)
$ qgdel @myjobgroup
(Will remove a permanent jobgroup.)
(Will kill all jobs inside the job group. Only for auto created @jobgroups the @jobgroup will vanish afterwards.)
$qalter -g "" <jobid>
(Remove the binding to a group. [-gu-gp like above])
$ qalter -g @mygroup <jobid>
(Bind a job to a group. [-gu-gp like above]))
To unsubscribe from this discussion, e-mail: [issues-unsubscribe at gridengine.sunsource.net].
More information about the gridengine-users