2023-06-06: Ci::CancelRedundantPipelinesWorker saturating patroni-ci primary CPU with slow query
Customer Impact
Delays in background processes affecting the ability to merge requests and/or updating MRs after a push.
Current Status
2023-06-08 12:30 UTC: The incident is resolved following gitlab-org/gitlab!122764 (merged) and no longer deferring jobs
We noted delays in background processes, affecting the ability to merge requests. The problem cause was identified, and a fix was implemented by disabling the redundant pipeline cancellation
jobs. The sidekiq backlog has cleared, and services are performing as expected. The issue is currently mitigated
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.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: MRs not being updated after a push or delays in merging MRs
- Service Impact: ServiceAPI ServiceWeb ServiceGit ~"Service::Background Processing"
- Impact Duration:
2023-06-06 08:31 UTC - 2023-06-06 09:15 UTC
duration in minutes: 43 - Root cause: RootCauseSaturation Slow queries in redundant pipelines service causing saturation
📚 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 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.