Opened 10 years ago

Closed 8 years ago

#695 closed defect (fixed)

IZ3079: Man page entry for SCHEDULER_TIMEOUT incorrectly states that default is 600

Reported by: jf222792 Owned by:
Priority: normal Milestone:
Component: sge Version: 6.2u2
Severity: minor Keywords: Sun man
Cc:

Description

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

        Issue #:      3079             Platform:     Sun      Reporter: jf222792 (jf222792)
       Component:     gridengine          OS:        All
     Subcomponent:    man              Version:      6.2u2       CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    jf222792 (jf222792)
      QA Contact:     andreas
          URL:
       * Summary:     Man page entry for SCHEDULER_TIMEOUT incorrectly states that default is 600
   Status whiteboard:
      Attachments:

     Issue 3079 blocks:
   Votes for issue 3079:


   Opened: Wed Jul 8 07:24:00 -0700 2009 
------------------------


SGE_CONF(5) in 6.2u2_RC2, under qmaster_params:

     SCHEDULER_TIMEOUT
          Setting this parameter allows the scheduler  GDI  event
          acknowledge  timeout  to  be  manually  configured to a
          specific value. Currently the default value is  set  to
          10 minutes. The SCHEDULER_TIMEOUT value is specified in
          seconds.

This is slightly misleading. The default value is 10 minutes with
default scheduler configuration, but the default depends on the scheduler configuration.

More precisely, the default value for the SCHEDULER_TIMEOUT is 10 times the event delivery interval, capped between 600 and 1200 seconds.
*** (#1 of 1): 2009-02-18 14:07:15 CET thomas.dehn@sun.com

Change History (1)

comment:1 Changed 8 years ago by dlove

  • Resolution set to fixed
  • Severity set to minor
  • Status changed from new to closed

Fixed in
JF-2009-07-08-0: Bugfix: Man page should mention reprioritize_interval is

Note: See TracTickets for help on using tickets.