Opened 11 years ago
Last modified 10 years ago
#760 new defect
IZ3212: default_duration INFINITY in scheduler shouldn't start backfilling
Reported by: | reuti | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.2u4 |
Severity: | Keywords: | Macintosh scheduling | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=3212]
Issue #: 3212 Platform: Macintosh Reporter: reuti (reuti) Component: gridengine OS: All Subcomponent: scheduling Version: 6.2u4 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: DEFECT Target milestone: --- Assigned to: andreas (andreas) QA Contact: andreas URL: * Summary: default_duration INFINITY in scheduler shouldn't start backfilling Status whiteboard: Attachments: Issue 3212 blocks: Votes for issue 3212: Opened: Wed Dec 9 12:58:00 -0700 2009 ------------------------ Observed behavior: - submit jobs with no h_rt requested but request a consumable resource - the last job will in addition request a complex with high urgency, resource reservation and a huge amount of the consumable resource - this last job will skip to top of waiting jobs, but smaller requests always slip in from the former jobs Giving every job a dedicated runtime of 5 minutes gives the expected behavior: last job will reserve the consumable resource. The problem might be in the default_duration being INFINITY and other jobs which also are seen with an estimated runtime of INIFINTY are allowed to start backfilling. There should be a different entry UNDEFINED (maybe also as value for -l h_rt=). Other UNDEFINED jobs shouldn't be eligible for backfilling to avoid starvation in the default configuration. They can of course be scheduled when there was a job submitted with an explicit -l h_rt=INFINITY. Workaround for now: set the default_duration to 9999:00:00 instead of INFINITY
Note: See
TracTickets for help on using
tickets.