[
https://issues.apache.org/jira/browse/WHIRR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064706#comment-13064706
]
Soren Macbeth commented on WHIRR-260:
-------------------------------------
Hi Guys,
AWS was having issues last night filling spot requests, possibly related to the
change in pricing by AZ rather then region (just speculation on my part), in an
case, I tested the patch out while this was happening. Once the requests timed
out, there was an issue where the previously unfilled spot requests weren't
canceled, and entirely new set of requests were issued. This would be
undesirable behaviour, so if possible whirr should catch the timeouts and clean
up any outstanding open, but unfilled spot requests and cancel them.
FYI - We (Yieldbot) also use spot based instances for our production hadoop
clusters. We use a custom forked version of the python contrib scripts + a
patch for spot instances based on BackType's work. We also use the trick of
setting our bid price above the actual reserved instance price, but this isn't
100% successful, price spikes can still take out some instances, or prevent
requests being filled, but it works well most of the time.
> Support Spot Instances
> ----------------------
>
> Key: WHIRR-260
> URL: https://issues.apache.org/jira/browse/WHIRR-260
> Project: Whirr
> Issue Type: New Feature
> Reporter: Adrian Cole
> Assignee: Andrei Savu
> Fix For: 0.6.0
>
> Attachments: WHIRR-260.patch, WHIRR-260.patch
>
>
> note java support is via jclouds, scheduled for beta-10 release
> https://github.com/jclouds/jclouds-examples/tree/master/ec2-computeservice-spot
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
