2021-02-24: Jobs stuck pending on shared runners
Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in out handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.
Summary
We have been seeing slowness with Shared Runners on GitLab.com picking up jobs. Initial error rates have recovered, but we are handling further problems as we work through the backlog of jobs.
Timeline
All times UTC.
View recent production deployment and configuration events (internal only)
2021-02-24
-
15:36
- @cleveland declares incident in Slack.
Corrective Actions
- gitlab-org/gitlab-runner#27613 (closed) to see if we are doing something wrong when we face rate limits that ends up delaying the recovery of the fleet.
- One other corrective action when can take is to experiment with
MaxGrowthRate
.The maximum number of machines that can be added to the runner in parallel. Defaults to 0 (no limit)
so we can prevent us from reaching the API limits since we try to create a large amount of machines at the same time. (this was done as part of #3840 (closed))
Click to expand or collapse the Incident Review section.
Incident Review
Summary
- Service(s) affected:
- Team attribution:
- Time to detection:
- Minutes downtime or degradation:
Metrics
Customer Impact
-
Who was impacted by this incident? (i.e. external customers, internal customers)
- ...
-
What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
- ...
-
How many customers were affected?
- ...
-
If a precise customer impact number is unknown, what is the estimated impact (number and ratio of failed requests, amount of traffic drop, ...)?
- ...
What were the root causes?
Incident Response Analysis
-
How was the incident detected?
- ...
-
How could detection time be improved?
- ...
-
How was the root cause diagnosed?
- ...
-
How could time to diagnosis be improved?
- ...
-
How did we reach the point where we knew how to mitigate the impact?
- ...
-
How could time to mitigation be improved?
- ...
-
What went well?
- ...
Post Incident Analysis
-
Did we have other events in the past with the same root cause?
- ...
-
Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
- ...
-
Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
- ...
Lessons Learned
Guidelines
Resources
- If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)
Incident Review Stakeholders
Edited by John Jarvis