Hi Justin,<div><br></div><div>I again tried creating 30 nodes cluster and figured out something new. I am waiting for last 20 min for the cluster to be up. </div><div>I get the below message. Currently in EC2 all the nodes are up and running ,i don't know which node is taking time for SSH configuration.</div>
<div>so i am not able to restart or terminate a node. </div><div><br></div><div><div>>>> Using default cluster template: smallcluster</div><div>>>> Validating cluster template settings...</div><div>>>> Cluster template settings are valid</div>
<div>>>> Starting cluster...</div><div>>>> Launching a 30-node cluster...</div><div>>>> Creating security group @sc-smallcluster...</div><div>Reservation:r-0e2d7060</div><div>>>> Waiting for cluster to come up... (updating every 30s)</div>
<div>>>> Waiting for all nodes to be in a 'running' state...</div><div>29/29 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| 100% </div><div>>>> Waiting for SSH to come up on all nodes...</div>
<div>28/29 |------------------------------------------------------------- | 96% </div><div><br></div><div><br></div><div>Regards</div><div>Sumita</div><br><div class="gmail_quote">On Tue, Nov 8, 2011 at 7:42 PM, Justin Riley <span dir="ltr"><<a href="mailto:jtriley@mit.edu">jtriley@mit.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hi Sumita,<br>
<br>
Were you using spot instances? If not I believe there's a default
limit of 20 instances by default for flat-rate instances which
*could* be related to your issue. With spot instances you can create
up to 100 instances by default. So, if you need more than 20 nodes
and do not wish to submit a request to Amazon to increase your
flat-rate instance limit, you should be using spot instances:<br>
<br>
$ starcluster start -s 30 -b 0.50 mycluster<br>
<br>
With that said, StarCluster has no limit to the number of nodes you
can create, however, as you've seen, sometimes EC2 instances can
take longer to become 'running' than usual. Unfortunately this is
purely an EC2 back-end issue that cannot be resolved directly by
StarCluster. In my experience 22 minutes *is* quite a while to wait
for any instance to come up, however, I have had instances take up
to 15 min before in the past so this is not a total surprise to me.<br>
<br>
In the future if you run into this problem of waiting for an
instance to change from 'pending' to 'running' for too long (e.g.
15min+) I would recommend simply terminating the faulty instance
from the AWS console and then restart the cluster using:<br>
<br>
$ starcluster restart mycluster<br>
<br>
This should reboot all the currently running instances and begin
configuring the cluster and avoid having to terminate the entire
cluster and lose instance hours.<br>
<br>
HTH,<br>
<br>
~Justin<div><div></div><div class="h5"><br>
<br>
On 11/8/11 6:39 AM, Sumita Sinha wrote:<br>
<span style="white-space:pre-wrap">> Hello ,<br>
><br>
> Currently working with starcluster on EC2.<br>
><br>
> Tried creating a cluster with 30 nodes of type m1.small using
AMI - ami-8cf913e5.<br>
> Cluster creation was never completed as i found out that one
node node025 was showing pending status.<br>
> I waited for almost 22 minutes then terminated the cluster.<br>
> Cluster was terminated properly. Is there any limit to the
creation of nodes .<br>
><br>
><br>
><br>
><br>
> -- <br>
> Regards<br>
> Sumita Sinha<br>
><br>
></span><br>
<br></div></div>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.11 (Darwin)<br>
Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
<br>
iEYEARECAAYFAk65OL4ACgkQ4llAkMfDcrm9MACghU/Ey4v653fsD8XmpbQKONNp<br>
vdkAniIfFExWjqGAOWRolMrtePHfl4AL<br>
=Q8NI<br>
-----END PGP SIGNATURE-----<br>
<br>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Regards<br>Sumita Sinha<br><br><br>
</div>