Hi Jeff,<div>Your assumption seems correct. I know a lot about ELB but very little about plugins. I know Justin is still very busy so may not get to your question soon.</div><div><br></div><div>From the looks of things, you could add plugin code to:<br>
starcluster/cluster.py : line 788-789</div><div><br></div><div>OR</div><div><br></div><div>starcluster/clustersetup.py: line 473</div><div><br></div><div>As a stop gap until there is time to add something more formal and check it in.<br>
Let us know if that works for you temporarily.</div><div>Raj</div><div><br></div><div><br><div class="gmail_quote">On Mon, Feb 21, 2011 at 2:50 PM, Jeff White <span dir="ltr"><<a href="mailto:jeff@decide.com">jeff@decide.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I believe there is a race condition when nodes are added via the loadbalancer. The configured plugins are run after the new node is added to SGE. The issue is our plugin needs to do some setup on the new node before jobs get submitted to the new node. It would be better if plugins were run before the node is available to run jobs. If there is a use case for running a plugin after the node is added to SGE, then more hooks should be added, e.g. on_add_node_before_sge(), on_add_node_after_sge().<br>
<font color="#888888">
<br>jeff<br>
</font><br>_______________________________________________<br>
StarCluster mailing list<br>
<a href="mailto:StarCluster@mit.edu">StarCluster@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/starcluster" target="_blank">http://mailman.mit.edu/mailman/listinfo/starcluster</a><br>
<br></blockquote></div><br></div>