[GE issues] [Issue 3054] New - job reprioritization doesn't work as expected when there are jobs with and without tickets

joga Joachim.Gabler at sun.com
Tue Jun 16 13:54:16 BST 2009

                 Issue #|3054
                 Summary|job reprioritization doesn't work as expected when the
                        |re are jobs with and without tickets
       Status whiteboard|
              Issue type|DEFECT
             Assigned to|pollinger
             Reported by|joga

------- Additional comments from joga at sunsource.net Tue Jun 16 05:54:14 -0700 2009 -------
When I have job reprioritization activated, and run my cluster in overload (more cpu bound jobs than cpus), the reprioritization is broken
in the following scenario:

I have 2 Projects, A and B, having functional shares of 10 and 20.

In the scheduler config, I have
reprioritize_interval             00:00:40
weight_tickets_functional         1000000

One queue instance available, with 4 slots.

I submit the following jobs:
qsub -P A $SGE_ROOT/examples/jobs/worker.sh
qsub -P B $SGE_ROOT/examples/jobs/worker.sh
qsub $SGE_ROOT/examples/jobs/worker.sh
qsub $SGE_ROOT/examples/jobs/worker.sh

I would expect the job of project B getting significantly more cpu (double) than the job of project A, and the jobs without project getting
very low cpu.

I see the jobs without project getting very low cpu,
but the jobs for projects A and B get the same cpu, and they have the same nice value.

When I only submit jobs having a project it works as expected:
qsub -P A $SGE_ROOT/examples/jobs/worker.sh
qsub -P B $SGE_ROOT/examples/jobs/worker.sh

I see the job for project B getting arround twice the cpu as the job for project A, 
which is what I would expect. The jobs nice values are adjusted regularly to ensure they get the granted shares.


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

More information about the gridengine-users mailing list