2023-07-04: Increase in frequency of Gitaly GRPC ResourceExhausted errors causing 500 errors for clients
Customer Impact
A customer has reported (ZD internal link) an increase over recent weeks in the frequency of 500 errors being returned to API requests made to gitlab.com.
Looking at the logs I see 500 errors for the customer's namespace corresponding to Gitaly errors indicating timeouts.
Rails errors: https://log.gprd.gitlab.net/goto/2b51ec20-1ac6-11ee-a017-0d32180b1390
Gitaly errors: https://log.gprd.gitlab.net/goto/43f54ba0-1ac6-11ee-8afc-c9851e4645c0
Looking over the last week shows this pattern in Gitaly errors containing string "timed out" across all namespaces:
I don't believe these are the result of GRPC rate limiting.
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.
📚 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.