Closed Bug 1311475 Opened 8 years ago Closed 8 years ago

ATMO V2: Increase Spot Instance limits

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: chutten, Unassigned)

References

Details

User Story

According to [0] the default limit is 20, and we need to apply for more. This is confirmed in our console [1].

[0] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-spot-limits.html
[1] https://us-west-2.console.aws.amazon.com/ec2/v2/home?region=us-west-2#Limits:
jobflow id j-2KJCSH8Y4H78Q
Well this isn't good: "The requested number of spot instances exceeds your limit"
User Story: (updated)
Summary: ATMO V2: Tried to start a cluster, got TERMINATED_WITH_ERRORS → ATMO V2: Increase Spot Instance limits
Flags: needinfo?(bimsland)
Severity: normal → blocker
Request for 500: https://console.aws.amazon.com/support/home?region=us-west-2#/case/?displayId=1916825841&language=en

These requests usually take a day or two. I understand that spot support is new functionality, so perhaps it can be disabled temporarily if this can't wait until Monday.
Flags: needinfo?(bimsland)
Looks like it's been approved, thanks whd.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.