Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spot instances are not created #12

Open
sai-tirunagiri opened this issue May 21, 2018 · 3 comments
Open

Spot instances are not created #12

sai-tirunagiri opened this issue May 21, 2018 · 3 comments

Comments

@sai-tirunagiri
Copy link

Hi,

Even after changing the instance types, not able to create spot instances. Is there any method that I should be following before creating the fleet.?

  • I dont see any instances running in spot instances.
  • in the history it says:
    allLaunchSpecsTemporarilyBlacklisted | Several attempts to launch instances have failed. Either the request could not be satisfied or the configuration is not valid. We will retry the request again later. For more information, see the description of the event.
    -- | --

Is there a way, instead of spot instances, create just an instance - EC2 and run the containers in it.?

Please advice.

Thanks

@robertoriv
Copy link
Collaborator

It looks like your instance type and price combination might have not matched anything available for Spot. One thing to try is to go through the SpotFleet wizard, tell it the instance size you want and how many. It will tell you what bid price to put in. With that information you can update the NodeInstanceType and MaxSpotBidPrice parameters for the stack.

If you want to use regular EC2 instance, the README mentions that it is an option:

An AutoScaling Group is also provided as fall-back; in case Spot Fleet doesn't fit your needs. All you need to do is scale it up.

The AutoScaling Group is created automatically for you. You just need to find it in the EC2 console, edit its settings (set its desired capacity to any number other than 0) and instances should come up.

@sharath-yml
Copy link

I had the same issue. I got it fixed after I increased the disk/volume size. Your selected AMI might require bigger volume size than specified. I am using Terraform though.

@robertoriv
Copy link
Collaborator

@sharath-yml thanks for the info. We used to run these in a "production" deployment with 22GB, but eventually upped the number to 100GB because the nodes were eating into the IOPS and the instances went unresponsive.

That's how this ended up as a parameter:

  DockerVolumeSize:
    Type: Number
    Default: 22
    Description: Size (in GiB) of the EBS volume that Docker users for image and metadata storage.  # https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-ami-storage-config.html

@sai-tirunagiri are you still having issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants