[GE issues] [Issue 3281] consumable JOB handled as YES during scheduling, but correctly charged at execution time

reuti reuti at staff.uni-marburg.de
Sun Aug 29 16:52:06 BST 2010


User reuti changed the following:

                What    |Old value                 |New value
                 Summary|Complex EXCL with consumab|consumable JOB handled as 
                        |le JOB needs completely fr|YES during scheduling, but
                        |ee nodes during scheduling| correctly charged at exec
                        |                          |ution time

------- Additional comments from reuti at sunsource.net Sun Aug 29 08:52:03 -0700 2010 -------
The same applies also for normal JOB consumables, when a load_threshold is used:

$ qconf -sc
#name               shortcut   type        relop   requestable consumable default  urgency 
master              mst        INT         <=      YES         JOB        1        1000

One queue with slots=4 across two nodes with each:

$ qconf -se pc15370
complex_values        master=2

Running job: qsub -pe mpich 4 test.sh

$ qstat -F master
queuename                      qtype resv/used/tot. load_avg arch          states
all.q at pc15370.Chemie.Uni-Marbu BIP   0/2/4          0.06     lx24-x86      
   2312 1.75000 test.sh    reuti        r     08/29/2010 17:32:13     2        
all.q at pc15381.Chemie.Uni-Marbu BIP   0/2/4          0.02     lx24-x86      
   2312 1.75000 test.sh    reuti        r     08/29/2010 17:32:13     2 

this is correct. But now with a: load_thresholds       master=1

$ qstat -j 2313
scheduling info:            cannot run in PE "mpich" because it only offers 2 slots

`qalter` output is misleading like in the former case complaining about "no suitable queues". Removing the load_threshold will start the job.

(In the real case I want to block other queues, but this example is a shrink down version. In contrast to issue 464 load_threshold are now
already fulfilled for "<=", not only "<" - this must have  been changed at one time. But this is a different thing.)


To unsubscribe from this discussion, e-mail: [issues-unsubscribe at gridengine.sunsource.net].

More information about the gridengine-users mailing list