@nchammas would this solve the problem that occurs when launching a spot instance cluster and one of the nodes ends up getting terminated which ends in the launch command just hanging forever? Or should I submit a new issue for that case?

@engrean - Have you seen this issue since d5b086c made it in? Flintrock should now immediately error out as soon as a spot request fails.

You'll need to be running on master to get this fix.

If you're still seeing the issue, the yes, please submit a new issue so we can look into it. I'd be curious to see where exactly the launch hangs, for example.

Would love to have this feature. It would be great to be able to specify a different instance type for the master as well.

Would it make sense to separate the add-slaves logic from launch? In other words, the workflow would be to create a master instance only first and then add all the slaves of any type you want to it with a second call.

Seconding the "would love this feature", and even more so, being able to specify different master and slave instance types.

@nchammas is there any progress on this?

@mblack20 - Nope. The current workaround, I believe, is to launch a regular cluster with no slaves, and then add spot slaves separately using add-slaves.