Opened 13 years ago

Last modified 9 years ago

#318 new enhancement

IZ1954: Apply job priorities to cluster queues

Reported by: mbrown3 Owned by:
Priority: low Milestone:
Component: sge Version: 6.0u7
Severity: Keywords: scheduling
Cc:

Description

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

        Issue #:      1954             Platform:     All           Reporter: mbrown3 (mbrown3)
       Component:     gridengine          OS:        All
     Subcomponent:    scheduling       Version:      6.0u7            CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    sgrell (sgrell)
      QA Contact:     andreas
          URL:
       * Summary:     Apply job priorities to cluster queues
   Status whiteboard:
      Attachments:

     Issue 1954 blocks:
   Votes for issue 1954:


   Opened: Wed Jan 4 12:15:00 -0700 2006 
------------------------


Currently, jobs can be prioritized by user, project, department, or job.  This
enhancement requests the ability to also prioritize jobs by cluster queue.

Currently, when submitting jobs to cluster queues that subordinate each other,
priority 'bands' must be configured by project to enforce desired scheduling.
See:  http://gridengine.sunsource.net/servlets/ReadMsg?msgId=9820&listName=users

However, this only allows jobs to execute with the correct priority in cluster
queues with certain project settings.  This effectively locks certain cluster
queues to certain projects, preventing some desirable configurations.  By
removing this restriction, jobs will be assigned a correct priority based on the
cluster queue they actually use.

   ------- Additional comments from andreas Wed Jan 11 08:16:55 -0700 2006 -------
WORKAROUND:
The state-of-the-art workaround for 6.0 is descibed under
http://gridengine.sunsource.net/servlets/ReadMsg?listName=users&msgNo=12771
it bases on use of enforced per-queue urgency resources and should provide a
reasonable solution. The only change for end-users is that the per-queue urgency
resource attribute needs to be requested via -l queue_attr rather than -q queue.

Lowering priority to P4.

Change History (0)

Note: See TracTickets for help on using tickets.