Opened 15 years ago

Last modified 11 years ago

#374 new enhancement

IZ2087: No user setting for custom default_duration, i.e. not enforced h_rt/s_rt

Reported by: reuti Owned by:
Priority: normal Milestone:
Component: sge Version: 6.0u7
Severity: Keywords: kernel


[Imported from gridengine issuezilla]

        Issue #:      2087             Platform:     All           Reporter: reuti (reuti)
       Component:     gridengine          OS:        All
     Subcomponent:    kernel           Version:      6.0u7            CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
       * Summary:     No user setting for custom default_duration, i.e. not enforced h_rt/s_rt
   Status whiteboard:

     Issue 2087 blocks:
   Votes for issue 2087:

   Opened: Thu Jul 20 14:37:00 -0700 2006 

If no h_rt/s_rt is set in the submission command, the default_duration is taken for the reservation
calculation. The h_rt/s_rt if specified  are enforced, while the default_duration is only a hint for the

There is no option for the user, if he/she wants to give a different value for the estimated job duration,
which is not enforced. This could be:

1) Another option to qsub, like -et (estimated time), and an admin-flag to (dis-)allow its setting.

2) Options to the execd in the SGE configuration, to redefine the used signals for warning the job when
the soft limit is reached (i.e. the requested -l s_rt,...) like it can already be done for the notify signals
(WARN_RT=, WARN_CPU=, WARN_VMEM= with the value NONE besides signals)

Workaround for now: request only -l s_rt and trap the generated signal in the jobscript and the called

   ------- Additional comments from andreas Fri Jul 21 02:50:22 -0700 2006 -------
Good RFE. Instead of new -et qsub(1) option proposed in 1) a new resource limit
such as -l duration=1:: could be defined. For per user defaults
$HOME/.sge_request could be used.

If we had such a limit we could also support
optional DRMAA job template attribute 'drmaa_run_duration_slimit'.

The change itself could be made in job_get_duration() in daemons/schedd/scheduler.c.

   ------- Additional comments from templedf Tue Jan 13 07:00:48 -0700 2009 -------
*** Issue 2571 has been marked as a duplicate of this issue. ***

Change History (0)

Note: See TracTickets for help on using tickets.