2024-01-26: saas_runner_queues SLI of the ci-runners service (main stage) has an apdex violating SLO
Customer Impact
Some jobs for customers were in pending state between 5min-15min for the saas-linux-small-amd64 shard.
Current Status
This recovered on it's own, we see when we had a spike of jobs, we ran out of idle machines, so we couldn't pick up jobs:
So we have the following timeline:
-
2024-01-26 01:16:00: Large number of jobs started getting scheduled -
2024-01-26 01:17:00: Ran out of Idle VMs, so we no longer pick up jobs -
2024-01-26 01:17:00: Apdex dropped
📚 References and helpful links
Recent Events (available internally only):
- Feature Flag Log - Chatops to toggle Feature Flags Documentation
- Infrastructure Configurations
- GCP Events (e.g. host failure)
Deployment Guidance
- Deployments Log | Gitlab.com Latest Updates
- Reach out to Release Managers for S1/S2 incidents to discuss Rollbacks, Hot Patching or speeding up deployments. | Rollback Runbook | Hot Patch Runbook
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
- Corrective action ❙ Infradev
- Incident Review ❙ Infra investigation followup
- Confidential Support contact ❙ QA investigation
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 our 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.
Security Note: If anything abnormal is found during the course of your investigation, please do not hesitate to contact security.