Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-11931

Spot instances aren't being created in the correct availability zone

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 4.3
    • 4.1.2
    • Elastic Bamboo
    • OnDemand 4.1.2-ondemand-rc9

      Currently when an elastic instance is created using spot instances, the availability zone preference isn't being used for the spot request. This means EC2 randomly picks the AZ to put the instance in causing unwanted data transfer costs.

      If you look at the screen shots you'll see my preference was us-east-1d however the spot request that was generated had an empty AZ field.

            [BAM-11931] Spot instances aren't being created in the correct availability zone

            Another issue this causes is certain EC2 zones have traditionally higher variability in pricing (spikes) then others. If I set my preferred zone and pricing based on that zone and you create the request in a different zone the probability of it being shut down because the price went up too high is much greater. This is happening a lot to me today.

            Chris Spradlin added a comment - Another issue this causes is certain EC2 zones have traditionally higher variability in pricing (spikes) then others. If I set my preferred zone and pricing based on that zone and you create the request in a different zone the probability of it being shut down because the price went up too high is much greater. This is happening a lot to me today.

            Hi Chris,

            Thanks for reporting this. Ive added this to our backlog of ec2 issues to look at for OnDemand customers.

            James

            James Dumay added a comment - Hi Chris, Thanks for reporting this. Ive added this to our backlog of ec2 issues to look at for OnDemand customers. James

            Still, these are only regional changes ($0.01 per GB).

            Przemek Bruski added a comment - Still, these are only regional changes ($0.01 per GB).

              Unassigned Unassigned
              4266f0f1452d Chris Spradlin
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: