2023-10-30: Gitlab.com is down
Incident review issue: #17057 (closed)
Customer Impact
The primary database for GitLab.com was saturated due to a spike in bulk import jobs. This caused an intermittent disruption in accessing GitLab.com including web services, API services, and Git operations. These services have now all recovered.
Incident doc (deprecated)
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.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: Intermittent disruption in accessing GitLab.com including web services, API services, and Git operations.
- Service Impact: ServiceWeb ServiceAPI ServiceGit ServiceSidekiq ServicePatroni
- Root cause: Database saturation on the merge_requests table caused by bulk import jobs. #17054 (comment 1627154963). Supporting importing in batches was introduced a few months ago.
- Impact Duration: 2023-10-30 15:27 UTC to 16:15 UTC. Duration of 48 minutes of service disruptions. This was declared mitigated later at 17:57 UTC after completing our investigation.
- Mitigation: We temporarily disabled import functionality for all of GitLab.com via the Admin setting. This prevented the creation of new import jobs and allowed us time to continue investigating.
- Resolution: The feature flag for
bulk_imports_batched_import_export
was disabled. Import functionality will now be using individual jobs rather than batched jobs. - Corrective Actions:
- https://gitlab.com/gitlab-org/gitlab/-/issues/429856+
- Mark relevant Direct Transfer workers as `defe... (gitlab-org/gitlab#429871)
- https://gitlab.com/gitlab-org/gitlab/-/issues/429863+
- https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/2597+
📚 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.