Closed
Bug 1422301
Opened 8 years ago
Closed 8 years ago
EC2 bids failing with price-too-low and capacity-overcommitted
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1422081
People
(Reporter: dustin, Unassigned)
Details
This:
https://aws.amazon.com/blogs/aws/amazon-ec2-update-streamlined-access-to-spot-capacity-smooth-price-changes-instance-hibernation/
started at about the same time as this week's provisioning issues (behind bug 1422295 and that led earlier to noticing bug 1421618): spot requests are failing for "price-too-low", which shouldn't happen if we're using "real" pricing data -- but I assume the "smoothed" pricing data is a marketing term for "fake" pricing data.
We're also getting a lot of "capacity-overcommitted" (or something of the sort) which suggests to me that AWS is out of capacity. And that would make sense if reserved instance prices just dropped to spot prices -- everyone will pile in and use all of the available capacity.
Anyway, eu-central-1 seemed to have the least capacity, and we removed it from a few workerTypes and saw them perform better.
| Reporter | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Updated•8 years ago
|
Mentor: dustin, helfi92
Summary: Adjust to the new world of spot requests → EC2 bids failing with price-too-low and capacity-overcommitted
| Assignee | ||
Updated•6 years ago
|
Component: AWS-Provisioner → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•