2023-05-17: High error rate in Git

Customer Impact

Failed git commands like git clone/fetch/push

Current Status

The error spike auto-resolved on its own. GitLab workhorse is failing to connect to all the Gitaly servers which is causing timeouts. We've seen this happen last week around the same time as well in #14074 (closed) and #14087 (closed).

We will continue the investigation in https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/23740

📚 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.

Edited May 22, 2023 by Steve Xuereb
Assignee Loading
Time tracking Loading