Re: registering nodes with SGE after plugins run

From: Justin Riley <no email>
Date: Mon, 3 Mar 2014 16:05:49 -0500

Hi Christian,

The SGE plugin is a 'default' plugin that runs before all other plugins
for historical reasons. You can change this however by manually defining
the SGE plugin in your config, adding disable_queue=True to your cluster
config, and then adding the manually defined SGE plugin to your plugins
list in the order you prefer. For example:

[plugin sge]
setup_class = starcluster.plugins.sge.SGEPlugin

[plugin yourplugin]
setup_class = ...

[cluster smallcluster]
...
disable_queue = True
plugins = yourplugin, sge

This is similar to the instructions for 'Advanced Options' in the SGE
plugin docs:

http://star.mit.edu/cluster/docs/latest/plugins/sge.html#disabling-job-execution-on-master-node

With this config your plugin will run before the SGE plugin which should
solve your issue.

~Justin

On Mon, Mar 03, 2014 at 08:55:32PM +0000, Haselgrove, Christian wrote:
> I’m running into a quirk (um, or feature!) of starcluster that has been tripping me up. When I addnode fresh nodes to a cluster, the nodes are registered to SGE before my local plugins have run. Since these plugins install software needed for the jobs, if I addnode to a cluster with queued jobs, some of these jobs will be scheduled before the node is ready for them and will fail. Is it possible to get starcluster to register the node with SGE after the plugins have run?
>
> Thanks,
> Christian
>
> --
> Christian Haselgrove
> christian.haselgrove_at_umassmed.edu
> 774-455-4109
>
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster



Received on Mon Mar 03 2014 - 16:05:54 EST