[GE issues] [Issue 3212] New - default_duration INFINITY in scheduler shouldn't start backfilling
reuti at staff.uni-marburg.de
Wed Dec 9 19:58:28 GMT 2009
Summary|default_duration INFINITY in scheduler shouldn't start
------- Additional comments from reuti at sunsource.net Wed Dec 9 11:58:25 -0800 2009 -------
- 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
To unsubscribe from this discussion, e-mail: [issues-unsubscribe at gridengine.sunsource.net].
More information about the gridengine-users