[GE users] Using gridengine to administer the cluster
landman at scalableinformatics.com
Tue Aug 29 13:43:58 BST 2006
[ The following text is in the "ISO-8859-1" character set. ]
[ Your display is set for the "ISO-8859-10" character set. ]
[ Some special characters may be displayed incorrectly. ]
You would need to make sure the user had sudo capability on each node.
Last I remember, SGE doesn't allow root user to submit jobs.
You could generate the queue list with a simple qselect
[landman at minicc ~]$ qselect
all.q at compute-0-2.local
all.q at minicc.local
all.q at compute-0-0.local
all.q at compute-0-3.local
all.q at compute-0-1.local
Then very likely, you could do a simple for loop over the hosts using
qsub -q queue
foreach q (`qselect`)
qsub -q $q sudo -u root $@
Now here is why you might not want to do this.
1) if a queue goes down due to a machine crash, or somehow gets flushed
ahead of time, this could leave machine(s) in an odd state relative to
2) You have to set up sudo across your cluster. This is unfortunately
3) you don't have a guaranteed immediate execution of the administrative
You might want to look at pdsh for your cluster. It is a good tool
designed specifically to enable administration of large collections of
machines from a command line. To run /etc/init.d/lmsensors across a
cluster, you would
pdsh /etc/init.d/lmsensors start
Michael James wrote:
> Is there a way of scheduling a job
> so it gets run on each cluster node once?
> If I could do that I could use gridengine to administer
> the cluster, nodes could pull their own updates, etc.
> Just a thought...
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics LLC,
email: landman at scalableinformatics.com
web : http://www.scalableinformatics.com
phone: +1 734 786 8423
fax : +1 734 786 8452 or +1 866 888 3112
cell : +1 734 612 4615
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