On Wed, 5 Feb 2014, Reuti wrote:
...
This is for sure a matter of discussion. One could also argue, that
because of the E state the admin should take proper action and remove
the condition which caused the error. After this, the job should get the
priority it deserves to instantly. If it is a bigger problem, the admin
could put the job on hold. And this puzzles me more: although the job is
put on hold, it still keeps the priority it once got.
For other waiting jobs it's working: attaching and removing the hold
will recalculate the priority every time.
...
Hi Reuti,
Sorry, I'm not clear: are you agreeing or disagreeing?
I'm not sure of your argument about the job getting its deserved priority
instantly:- if it didn't attract priority while in 'E', it would get it at
the scheduling run after the state was cleared. Surely, this is all that
matters? Or is that what you meant?
Cheers,
Mark
(sorry for delay - got distracted on a training course)
--
-----------------------------------------------------------------
Mark Dixon Email : [email protected]
HPC/Grid Systems Support Tel (int): 35429
Information Systems Services Tel (ext): +44(0)113 343 5429
University of Leeds, LS2 9JT, UK
-----------------------------------------------------------------
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
