2024-10-25: The queuing_queries_duration SLI of the ci-runners service (cny stage) has an apdex violating SLO
Customer Impact
Runner requests to /api/v4/jobs/request are taking slightly longer than usual.
Current Status
A manual transaction that was triggered around Oct 24, 23:45 UTC caused the vaccume operation to fail on the CI database, which resulted in growing dead tuples. The transaction was cancelled around Oct 25 09:45 UTC, soon after the next vaccume suceeded and the dead tuples went down, which resolved the incident. More details about this transaction can be found in #18764 (comment 2178213885).
We anticipated worse impact at some point and raised the severity to severity2, but the user impact was minimal and we set this back to severity3.
More information will be added as we investigate the issue. For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates.
📚 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. 1.