Re: USERDATA_SCRIPTS not running with addnode
This archive was generated by
I am far from an StarCluster expert, but why not turn your scripts into a StarCluster plugin then add your plugin to your template's configuration? This discussion last month (http://star.mit.edu/cluster/mlarchives/2170.html
) discusses how to force you plugin to run before the new node is added to the OGE cluster. I would expect that the load balancer would respect the template configuration; however, I do not have practical experience using it.
From: starcluster-bounces_at_mit.edu [mailto:starcluster-bounces_at_mit.edu] On Behalf Of Cedar McKay
Sent: Wednesday, May 14, 2014 6:31 PM
Subject: [StarCluster] USERDATA_SCRIPTS not running with addnode
Sorry to bump myself, but this is really the biggest difficulty I'm having with starcluster at the moment. It makes it difficult to use the addnode function, and even harder (impossible) to use the Elastic Load Balancer.
As a general question, is there a place other than the USERDATA_SCRIPTS that I could use to execute scripts on each node's boot? I'm thinking of /etc/init.d on the boot image, or something like that, but I've been reluctant to modify areas where I suspect some starcluster magic might be happening.
> Hello all.
> I'm using the USERDATA_SCRIPTS setting to run a script on cluster start. It is mounting an s3fs volume if that matters, though I've also tested it with simply touching a file. As an aside, is there a better place to mount a volume? I didn't dare touch fstab because I figured it might be generate/changed by starcluster depending on the cluster config.
> In any case, it works as expected when starting a cluster, but if I use addnode, the new nodes don't execute the script. Is this a bug, or behavior that I can change? It seems to me that new nodes should be started in the exact same way as other nodes.
StarCluster mailing list
Received on Thu May 15 2014 - 13:52:33 EDT