Gitaly Service
- Service Overview
- Alerts: https://alerts.gitlab.net/#/alerts?filter=%7Btype%3D%22gitaly%22%2C%20tier%3D%22stor%22%7D
- Label: gitlab-com/gl-infra/production~“Service::Gitaly”
Logging
Section titled “Logging”Troubleshooting Pointers
Section titled “Troubleshooting Pointers”- ApdexSLOViolation
- TrafficAbsent and TrafficCessation
- ../cells/infra-development.md
- Validate Instrumentor Changes within Cells Infrastructure
- Cloudflare: Managing Traffic
- Disaster Recovery Gameday Schedule
- Google Cloud Snapshots
- Measuring Recovery Activities
- Zonal and Regional Recovery Guide
- ../elastic/advanced-search-in-gitlab.md
- Elastic Nodes Disk Space Saturation
- Deploying a change to gitlab.rb
- Workhorse Session Alerts
kasDisable Integrations- Service-Level Monitoring
- Tuning and Modifying Alerts
- ../monitoring/apdex-alerts-guide.md
- Service Apdex
- An impatient SRE’s guide to deleting alerts
- Session: Application architecture
- Gitlab.com on Kubernetes
- Diagnosis with Kibana
- Restore Gitaly data on
ops.gitlab.net - Pingdom
- A survival guide for SREs to working with Redis at GitLab
- High build pressure
- Pull Mirroring Timeout with Large LFS Files
- ../sidekiq/sharding.md
sidekiq_queueingapdex violation- Life of a Git Request
- Life of a Web Request
- Deleted Project Restoration
- ../uncategorized/namespace-restore.md
- Project exports
- Remove Blobs
- Ruby profiling
- How to upload a file to Google Cloud Storage from any system without a credentials configuration
- Find a project from its hashed storage path
- Copying or moving a Git repository by hand
- git-high-cpu-and-memory-usage.md
- Debugging gitaly with gitaly-debug
- Gitaly is down
- Gitaly error rate is too high
- Gitaly latency is too high
- Upgrading the OS of Gitaly VMs
- Gitaly profiling
- Gitaly Queuing
- Gitaly repository cgroups
- Restoring gitaly data corruption on a project after an unclean shutdown
- Gitaly Repository Export
- Gitaly token rotation
- Gitaly unusual activity alert
- Gitaly version mismatch
gitalyctl- Gracefully restart gitaly-ruby
- Moving repositories from one Gitaly node to another
- Gitaly multi-project migration
- Adding new storage capacity
- Gitaly Snapshot Verification
- GitLab Storage Re-balancing
- Managing GitLab Storage Shards (Gitaly)
Architecture
Section titled “Architecture”graph TD gprd-base-stor-gitaly-common-->gprd-base-stor-gitaly-cny gprd-base-stor-gitaly-common-->gprd-base-stor-gitaly gprd-base-stor-gitaly-->gprd-base-stor-gitaly-hdd gprd-base-stor-gitaly-->gprd-base-stor-gitaly-marqueegprd-base-stor-gitaly-common: The base configuration which is common for all Gitaly shards and stages.gprd-base-stor-gitaly-cny: Any extra configuration we might want to add for Gitalyshard=default, stage=cny.gprd-base-stor-gitaly: Any extra configuration we might want to add for Gitalyshard=default, stage=main.gprd-base-stor-gitaly-hdd: Any extra configuration we might want to add for Gitalyshard=hdd, stage=main.gprd-base-stor-gitaly-marquee: Any extra configuration we might want to add for Gitalyshard=marquee, stage=main.
graph TD gstg-base-stor-gitaly-->gstg-base-stor-gitaly-cny gstg-base-stor-gitaly-->gstg-base-stor-gitaly-hddgstg-base-stor-gitaly: The base configuration which is common for all Gitaly shards and stages.gstg-base-stor-gitaly-cny: Any extra configuration we might want to add for Gitalyshard=default, stage=cny.gstg-base-stor-gitaly-hdd: Any extra configuration we might want to add for Gitalyshard=main, stage=main.