Opened 10 years ago

Last modified 9 years ago

#735 new enhancement

IZ3162: Suspendable flag for jobs: -s y/n

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

Description

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

        Issue #:      3162             Platform:     All           Reporter: reuti (reuti)
       Component:     gridengine          OS:        All
     Subcomponent:    kernel           Version:      6.2u4            CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     Suspendable flag for jobs: -s y/n
   Status whiteboard:
      Attachments:

     Issue 3162 blocks:
   Votes for issue 3162:


   Opened: Tue Oct 13 11:35:00 -0700 2009 
------------------------


With the implementation of slotwise suspend, an attached flag to the submitted jobs could tell the scheduler, whether a particular job can be suspended, or is excluded from being a
candidate of the jobs which could get suspended. This should be (like the rerun-flag) changeable at runtime with qalter. If the job is right now in suspended state, it will only be
honored when the job would get suspended again after it continued.

The flag will only be honored by the automatic slotwise suspend by default. Suspending the complete queue or job with qmod will have preference (or adjustable with an entry in the in
the SGE config of "qmaster_params": "DISABLE_QMOD_SUSPENDABLE").

   ------- Additional comments from reuti Thu Feb 11 10:03:30 -0700 2010 -------
They value of this setting should somehow be available in an RQS. The idea behind it, is to limit the number of jobs a user has running
which are non-suspendable, while he is allowed to fill the complete cluster with suspendable jobs (or which are also limited). E.g.:

limit users {*} to non-suspendable-jobs=5
limit users {*} to jobs=20

would allow a total of 25.

With the mentioned facility of changing the value at runtime, it could lead to the situation that the qalter needs to state: "Changing of
suspendable setting would violate the defined quota. Command ignored."

Change History (0)

Note: See TracTickets for help on using tickets.