[gridengine users] Advance reservations and disabled nodes/queues
w.hay at ucl.ac.uk
Thu Feb 9 19:52:30 UTC 2012
On 9 February 2012 16:28, Sabine Kreidl <sabine.kreidl at uibk.ac.at> wrote:
> I'm experiencing (SGE 8.0.0a) that disabled nodes (we have only one
> queue) are added to advance reservations. As those nodes are usually
> disabled for a reason (defect hard drive, etc...) this is not what I
> would want to happen (especially if I want the reservation to start now).
> Is there a way or some workaround to make the scheduler avoid disabled
> nodes within advance reservations? I'd appreciate any advice.
We have a complex associated with every node called status that is
normally set to OK. When a node has a problem we set it to a
description of the problem instead. Our JSV ensures jobs always
request status=OK. With a similar complex you could request status=OK
when making the AR.
We also have a script that lists out nodes that aren't OK and their
status. Essentially duplicating the functionality of pbsnodes under
Torque. With this available as a permanent way to disable nodes we've
set queues to enabled at startup and use qmod -d to mean "disabled
till next reboot" only.
> users mailing list
> users at gridengine.org
More information about the users