2022-12-14: Sidekiq shard_urgent_cpu_bound saturated
Current Status
At 10:00 UTC
we saw delays in background processing for approximately 45 minutes that impacted both web and api. The primary impact was slower processing of CI jobs, issues, merge requests and notes.
The root cause was a feature-flag rollout [Feature flag] Rollout of `multi_pipeline_scan_... (gitlab-org/gitlab#382990 - closed) . As soon as the problem was identified, the feature was disabled which allowed us to resume normal background processing.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: Slower processing of CI jobs, issues, merge requests and notes for approximately 45 minutes
- Service Impact: ServiceWeb ServiceAPI
- Impact Duration:
10:00 UTC
-10:45 UTC
(45min) - Root cause: [Feature flag] Rollout of `multi_pipeline_scan_... (gitlab-org/gitlab#382990 - closed)
📚 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 and/or Hot Patching | 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 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.