Closed Bug 1495575 Opened 7 years ago Closed 6 years ago

servo-docker-worker without instances despite minCapacity=1 and pending tasks

Categories

(Taskcluster :: Operations and Service Requests, task)

Product:
Taskcluster
Component:
Operations and Service Requests
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: SimonSapin, Unassigned)

Details

servo-docker-worker doesn’t have a lot of traffic. Sometimes hours can go without a task. However when tasks do come we’d like to minimize latency. I’ve configured https://tools.taskcluster.net/aws-provisioner/servo-docker-worker/view with `minCapacity: 1` in the hope to help with that. However, it’s not rare to see aws-provisioner report pendingCapacity and runningCapacity both at zero, sometimes even if a task has been pending for longer than seems usually necessary for an EC2 instance to boot. (21 minutes as of this writing for https://tools.taskcluster.net/groups/Rt9LDLTuR56tKrOrH1bUMg/tasks/Rt9LDLTuR56tKrOrH1bUMg/runs/0 ) https://tools.taskcluster.net/aws-provisioner/servo-docker-worker/health shows some InsufficientInstanceCapacity and RequestLimitExceeded errors, but older than seems relevant. What’s wrong?
I don't think we have any way to know what happened, and I assume this has improved since this time..
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Component: Service Request → Operations and Service Requests
You need to log in before you can comment on or make changes to this bug.