2024-06-17: gitlab-org/gitlab pipelines get `fatal: remote error: GitLab is currently unable to handle this request due to load.` errors when cloning repository
Customer Impact
Failed jobs running for repos hosted on CNY gitlab, including the gitlab-org/gitlab
repo, can be mostly classified as internal.
Current Status
Jobs against gitlab-org/gitlab are intermittently erroring out due to the concurrency limits in Gitaly.
With the impact being limited to gitlab-org/gitlab
, this can point to an issue with the specific gitaly node hosting this repo, which happens to be accepting CNY traffic: gitaly-cny-01-stor-gprd
. Although ServiceCI Runners shouldn't be ruled out without further investigation (e.g. 2023-08-17: repeated pipeline failures with "fa... (#16193 - closed)).
Previous (recent) similar incidents include 2024-04-08: GitLab is currently unable to handl... (#17789 - closed). In summary, long-running backup processes were identified as the cause of a performance degradation on the canary server, and as a mitigation, the processes were killed and followup investigation was to be carried out to identify why the processes were running for so long, it is not clear whether that investigation took place.
Click to expand some related issues/MRs
It hasn't been confirmed whether this incident shares the same root cause as the aforementioned previous incident.
📚 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.
Security Note: If anything abnormal is found during the course of your investigation, please do not hesitate to contact security.e