2023-07-14: Intermittent apdex dips for web and patroni services due to row-level lock contention (#16042) · Issues · GitLab.com / GitLab Infrastructure Team / Production · GitLab (original) (raw)
GitLab Next
2023-07-14: Intermittent apdex dips for web and patroni services due to row-level lock contention
Customer Impact
Intermittent 5XX errors and performance degradation for 25 mins.
Current Status
We have identified the relevant code path and have rolled back to the last deploy which does not contain the offending code.
The code was calling a SQL query which is incorrectly constructed. This query was causing row-level lock contention, which was leading to performance issues.
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: Intermittent (3 waves) errors and high latency on gitlab-com.
- Service Impact: ServicePatroni ServiceWeb ServiceAPI ServiceCI Runners ServiceSidekiq
- Impact Duration: 00:51 UTC - 03:01 (~120 minutes) during which we had 25 minutes of complete downtime.
- Root cause: RootCauseSoftware-Change
📚 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.
Edited Jul 17, 2023 by Anthony Fappiano