[StarCluster] Max spot instance count exceeded

[MacMullan, Hugh]

Indeed! 5 is standard:

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-spot-limits.html

Defaults are stingy, but they are generally easily relaxed with a limit increase request (details in the link above).

Good luck!

-Hugh

On May 26, 2014, at 12:53, "Cedar McKay" <cmckay at uw.edu<mailto:cmckay at uw.edu>> wrote:

Amazon is very stingy with their max number of spot instances. For some types they only let you have a few spot instances. For example, I was limited to five high memory spot instances, but I asked them and they raised my limit to eight. In other words, I don't think there's anything wrong with star cluster.


Cedar

On May 26, 2014, at 9:38 AM, Torstein Fjermestad <tfjermestad at gmail.com<mailto:tfjermestad at gmail.com>> wrote:

Dear all,

when trying to add two new nodes to my cluster, I get the following error message:

Launching node(s): node006, node007
!!! ERROR - MaxSpotInstanceCountExceeded: Max spot instance count exceeded

The message is fairly obvious, but I find it suspicious because currently my cluster  only consists of one master node and four  slave nodes.

Is this really the maximum size of the cluster, or is the error message caused by something else?

Thanks in advance for your help.

Regards,
Torstein Fjermestad



_______________________________________________
StarCluster mailing list
StarCluster at mit.edu<mailto:StarCluster at mit.edu>
http://mailman.mit.edu/mailman/listinfo/starcluster

_______________________________________________
StarCluster mailing list
StarCluster at mit.edu<mailto:StarCluster at mit.edu>
http://mailman.mit.edu/mailman/listinfo/starcluster
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/starcluster/attachments/20140526/d36ef7a8/attachment.htm