2021-05-15: Increased "Maximum number of ci registered group runners (1000) exceeded" errors
Current Status
This has been fixed by disabling the feature flag. See the summary for more information.
Timeline
View recent production deployment and configuration events (internal only)
All times UTC.
2021-05-15
-
01:01
- @mbadeau declares incident in Slack.
Corrective Actions
Corrective actions should be put here as soon as an incident is mitigated, ensure that all corrective actions mentioned in the notes below are included.
- gitlab-org/gitlab#331030 (closed)
- Leave this feature flag off until the above is addressed: gitlab-org/gitlab#329438 (closed)
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.
Click to expand or collapse the Incident Review section.
Incident Review
Summary
We activated a feature flag earlier in the day to limit the creation of new runners once a namespace reaches 1000 registered runners. However, there were quite a few existing customers who were not aware that they had thousands of registered but inactive runners. These customers were then unable to register new runners and a few of them contacted support. It seems that there is something wrong with the process of de-registering runners, and it has been leaving a lot of stale runner registrations that are never getting cleaned up. We will need to address this before activating limits again.
- Service(s) affected: Runners
- Team attribution:
- Time to detection: 12 hours
- Minutes downtime or degradation: 12 hours
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
- Validate the number of runners per group before adding limits so we can evaluate the impact on customers.
Guidelines
Resources
- If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)