Opened 10 years ago

Last modified 8 years ago

#647 new feature

IZ2943: Job groups for easier handling of jobs which belong together

Reported by: reuti Owned by:
Priority: normal Milestone:
Component: sge Version: 6.2
Severity: Keywords: qmaster
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2943]

        Issue #:      2943             Platform:     All       Reporter: reuti (reuti)
       Component:     gridengine          OS:        All
     Subcomponent:    qmaster          Version:      6.2          CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    FEATURE
                                   Target milestone: ---
      Assigned to:    ernst (ernst)
      QA Contact:     ernst
          URL:
       * Summary:     Job groups for easier handling of jobs which belong together
   Status whiteboard:
      Attachments:
                      Date/filename:                                     Description:                                                              Submitted by:
                      Wed Mar 10 13:10:00 -0700 2010: SGE_Issue_2493.txt Job feedback notification thru email for group/related jobs. (text/plain) arvindpetaru

     Issue 2943 blocks:
   Votes for issue 2943:  3


   Opened: Tue Mar 3 09:26:00 -0700 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.)


$qdel @myjobgroup

    (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]))

   ------- Additional comments from arvindpetaru Wed Mar 10 13:10:39 -0700 2010 -------
Created an attachment (id=200)
Job feedback notification thru email for group/related jobs.

Attachments (1)

200 (274 bytes) - added by dlove 8 years ago.

Download all attachments as: .zip

Change History (1)

Changed 8 years ago by dlove

Note: See TracTickets for help on using tickets.