[GE users] taking hosts offline

templedf daniel.templeton at oracle.com
Wed Dec 29 00:22:43 GMT 2010


Another approach is to create a host group, e.g. @disabled, and an RQS 
that limits "hosts @disabled to slots=0".  To disable a host, just add 
it to the host group.  The benefit of this approach is that it works for 
all queues on the host without needing to enumerate them.

Daniel

On 12/22/10 03:13 PM, fx wrote:
> craffi<dag at sonsorol.org>  writes:
>
>> Hi Sebastian,
>>
>> Read the manpage for 'qmod' , you want the 'qmod -d all.q@<nodename>' --
>> this will (d)isable the node which allows running jobs to finish but
>> will prevent new work from landing.
>
> See http://www.nw-grid.ac.uk/LivScripts for a simple script
> (disable-nodes) which does that, and the reverse.  However, you might
> find it better to restrict the nodes to a specific ACL to allow testing
> them (e.g. sge-restrict-nodes from the same page); we'll often have such
> nodes running HPL to see if they stand up.  Note those scripts use node
> numbers, and work cross-cluster, courtesy of genders.  (I think there
> are similar things by other people lying around, but those are the ones
> I can point to.)
>

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=310598

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



More information about the gridengine-users mailing list