2022-09-27: Gitaly deployment failing on gstg
The DRI for this incident is the incident issue assignee, see roles and responsibilities.
For the assigned roles when the incident declared, see the Timelines tab. For timeline feedback see the dogfooding issue. To save time entering timeline events, use the quick action /timeline
.
Current Status
/var/log
is filing up in file-zfs-01-stor-gstg
, causing the deployment jobs to fail, example: https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/jobs/8089911.
In tracing the biggest files under /var/log
, it appears that /var/log/perf_build_id_cache/opt/gitlab/embedded/bin/gitaly
had around 277
copies of the gitaly binary each accounting for ~159M
, which is the main reason the disk was filled.
As a temporary mitigation /var/log/perf_build_id_cache
has been deleted, long term fix is being tracked in scalability#1937 (closed).
📚 References and helpful links
Recent Events (available internally only):
- Deployments ❙ Feature Flag Changes ❙ Gitlab.com Latest Updates
- Infrastructure Configurations
- GCP Events (e.g. host failure)
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
- 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.
Click to expand or collapse the Incident Review section.
Incident Review
-
Ensure that the exec summary is completed at the top of the incident issue, the timeline is updated and relevant graphs are included in the summary -
If there are any corrective action items mentioned in the notes on the incident, ensure they are listed in the "Corrective Action" section -
Fill out relevant sections below or link to the meeting review notes that cover these topics
Customer Impact
-
Who was impacted by this incident? (i.e. external customers, internal customers)
- ...
-
What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
- ...
-
How many customers were affected?
- ...
-
If a precise customer impact number is unknown, what is the estimated impact (number and ratio of failed requests, amount of traffic drop, ...)?
- ...
What were the root causes?
- ...
Incident Response Analysis
-
How was the incident detected?
- ...
-
How could detection time be improved?
- ...
-
How was the root cause diagnosed?
- ...
-
How could time to diagnosis be improved?
- ...
-
How did we reach the point where we knew how to mitigate the impact?
- ...
-
How could time to mitigation be improved?
- ...
-
What went well?
- ...
Post Incident Analysis
-
Did we have other events in the past with the same root cause?
- ...
-
Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
- ...
-
Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
- ...
What went well?
- ...
Guidelines
Resources
- If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)