Opened 14 years ago

Last modified 9 years ago

#206 new enhancement

IZ1311: PE should stay in once selected cluster-queue and PE seqno

Reported by: reuti Owned by:
Priority: normal Milestone:
Component: sge Version: 6.0u1
Severity: Keywords: scheduling
Cc:

Description

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

        Issue #:      1311             Platform:     Other         Reporter: reuti (reuti)
       Component:     gridengine          OS:        other
     Subcomponent:    scheduling       Version:      6.0u1            CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     PE should stay in once selected cluster-queue and PE seqno
   Status whiteboard:
      Attachments:

     Issue 1311 blocks:
   Votes for issue 1311:  2


   Opened: Thu Oct 28 09:33:00 -0700 2004 
------------------------


Symptom: You define two hostgroups and two
cluster-queues, to e.g. separate high speed
machines and low speed machines (one
hostgroup per queue). Attaching the same PE
to both queues may give the result, to get a
mix of slots from both queues.

(Depending on the used software, all slots
should have the same speed for a parallel job
instead)

Requested behavior: Once a queue is
selected for this PE, it should get only slots
from this queue. Maybe an option in the PE
definition to allow or disallow the mix, if the
former behavior (5.3 like) is still needed in
some cases.

Also any kind of putting a sort order for the PE
would be welcome. If they would stay in one
queue, there could be just one entry more
'pe_seqno' in the queue definition, and with a
similar behavior to seqno for slots, the PE
should first try to get into the one with the
lower number (i.e. using high speed
machines in the above example), and use the
other one only when there are no more
n-requested slots left.

   ------- Additional comments from andreas Thu Oct 28 10:08:12 -0700 2004 -------
Even though it's not a documented feature slots already are collected
preferably from a single queue instance. This is done in
parallel_sort_suitable_queues() when sorting queue instances by the
number of available slots per cluster queue (QU_tag). But I understand
there might be cases when explicitely disallowing mixes of queue
instances were desirable.

Changed summary to reflect PE seqno request.

   ------- Additional comments from reuti Tue Oct 25 08:13:43 -0700 2005 -------
As an extension to limit the scheduling only to one cluster queue, it would ease
the setup if you could limit the selection also to stay only in one @hostgroup
from the specified ones for this CQ.

   ------- Additional comments from sgrell Mon Dec 12 02:42:18 -0700 2005 -------
Changed subcomponent.

Stephan

Change History (0)

Note: See TracTickets for help on using tickets.