Re: sge submit host question
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
From: Chris Dagdigian <no email>
Date: Fri, 24 Feb 2012 15:58:29 -0500
It is *extremely* common for all SGE nodes in a cluster to be both admin and submit hosts.
The reason for making every node a submit host is that there are cluster workflows that often include jobs running on a node that either do new job submissions directly or else alter things like hold_jid or the parameters of a job array.
For small clusters that are persistant, the CLI command is "qconf -as <hostname>" to add a submit host.
Starcluster uses an SGE autoinstallation template file (I think ...) to automate the process of cluster building. Within this template file there is a parameter where you can list out your Admin and Submit hosts.
I imagine it would be pretty simple to customize or override the default StarCluster autoinstallation file so that all your nodes become submit host.
And if that is too complicated it's pretty trivial to iterate over the hostnames and run the "qconf -as" command ...
My $.02 of course!
-Chris
Received on Fri Feb 24 2012 - 15:58:36 EST
Date: Fri, 24 Feb 2012 15:58:29 -0500
It is *extremely* common for all SGE nodes in a cluster to be both admin and submit hosts.
The reason for making every node a submit host is that there are cluster workflows that often include jobs running on a node that either do new job submissions directly or else alter things like hold_jid or the parameters of a job array.
For small clusters that are persistant, the CLI command is "qconf -as <hostname>" to add a submit host.
Starcluster uses an SGE autoinstallation template file (I think ...) to automate the process of cluster building. Within this template file there is a parameter where you can list out your Admin and Submit hosts.
I imagine it would be pretty simple to customize or override the default StarCluster autoinstallation file so that all your nodes become submit host.
And if that is too complicated it's pretty trivial to iterate over the hostnames and run the "qconf -as" command ...
My $.02 of course!
-Chris
I ran into this too and found out I had to source
/etc/profile.d/sge.sh. I also am curious if there is a better solution,
presumably this is an interactive vs noninteractive shell issue.
-D
_______________________________________________
StarCluster mailing list
StarCluster@mit.edu
http://mailman.mit.edu/mailman/listinfo/starclusterHi,
This is more of a best-practice question.
Let's say I am on machine A. From it, I create a cluster. I can then
ssh into the "master" and launch jobs. Can this also be done from
machine A directly? I know one can do "starcluster sshmaster -u
sgeadmin <clustername> 'some command'" but then I typically run into
environment issues. Is there (simple) a way to make machine A an sge
submit host?
Chris
Dagdigian Principal Consultant, BioTeam Inc.
http://bioteam.net
My latest BioTeam Blog
Post: Metrum moves to the
cloud
(image/jpeg attachment: compose-unknown-contact.jpg)
(image/png attachment: slideshare.png)
(image/png attachment: twitter.png)
(image/png attachment: linkedin.png)
(image/png attachment: flickr.png)