[GE users] Preventing (almost) all new jobs.

Olesen, Mark Mark.Olesen at emcontechnologies.com
Thu Oct 30 09:53:50 GMT 2008

I have the following situation:

For testing purposes, I need complete access to the cluster, in
particular to some licenses.

One possibility would be to use qmod to disable and drain the queues.
I would presumably place a system hold on all the queued jobs, to
prevent them from executing when I re-enable the queues. Any jobs that
are submitted, while I need the cluster for testing, could presumably be
placed in hold state by adding an appropriate '-h' option to the global
sge_request. This has the slight problem that the users can simply
release the hold on their jobs - and ruin my testing.
Interestingly enough, it's not possible to place anything other than a
default user hold via the sge_request (GE-6.1u3).

If I go the more radical way and black-list entire Unix groups (while
permitting my own user), all of the submitted jobs are rejected
immediately.  This would be the less desirable solution.

How have others coped with this issue?

This e-mail message and any attachments may contain 
legally privileged, confidential or proprietary Information, 
or information otherwise protected by law of EMCON 
Technologies, its affiliates, or third parties. This notice 
serves as marking of its "Confidential" status as defined 
in any confidentiality agreements concerning the sender 
and recipient. If you are not the intended recipient(s), 
or the employee or agent responsible for delivery of this 
message to the intended recipient(s), you are hereby 
notified that any dissemination, distribution or copying 
of this e-mail message is strictly prohibited. 
If you have received this message in error, please 
immediately notify the sender and delete this e-mail 
message from your computer.

To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net

More information about the gridengine-users mailing list