2023-07-17: shard_urgent_cpu_bound SLI of the sidekiq service (main stage) has an apdex violating SLO
Customer Impact
The urgent CPU bound Sidekiq shard is responsible for running CPU intensive jobs that must be processed ASAP (for example: triggering a CI pipeline). Due to this incident, customers may have noticed a delay (< 1 min) in certain activities that are processed by this shard just after the hour every hour during off-peak times (approximately 19:00 to 07:00 UTC). For example, scheduled CI jobs that are set to run at minute 0 may have started running up to a minute after that. Approximately 500 jobs trigger every hour and approximately 60% of them may have been delayed up to a minute.
Current Status
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.