Opened 12 years ago

Last modified 11 years ago

#680 new enhancement

IZ3048: Enable a user-controlled limit number to limit a group of running jobs owned by the user

Reported by: templedf Owned by:
Priority: high Milestone:
Component: sge Version: 6.0u8
Severity: Keywords: scheduling


[Imported from gridengine issuezilla]

        Issue #:      3048             Platform:     All           Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    scheduling       Version:      6.0u8            CC:    None defined
        Status:       NEW              Priority:     P2
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
       * Summary:     Enable a user-controlled limit number to limit a group of running jobs owned by the user
   Status whiteboard:

     Issue 3048 blocks:
   Votes for issue 3048:

   Opened: Thu Jun 11 12:28:00 -0700 2009 

Up to the LSF 6.2 environment, non-manager users can create/manage/control job groups and submit jobs to a specific job group in order to
organize/manage their jobs.

However, with a new patch which will be released in a later version, customers reports that non-manager users can set the maximum number of
running jobs under a specific job groups. Any submitted jobs exceeding the limit number will be pending until any of the existing running
jobs finish.

According to customers, this feature is heavily used and is considered to be an important feature. Without this feature migration to Grid
Engine would be difficult.

The current release provides a way to set maximum number of running jobs per user under scheduler configuration via the maxujobs parameter.
However, with the current N1GE environment, it is not possible for non-manager users to set/modify any N1GE cluster configuration.

The new feature requesed in this RFE needs an ability for non-manager user to create/set/modify job groups including setting up a limit for
maximum number of running jobs under a job group.

   ------- Additional comments from templedf Thu Jun 11 12:28:56 -0700 2009 -------
Changed category to scheduling

Change History (0)

Note: See TracTickets for help on using tickets.