Repository Mirroring Service
- Service Overview
- Alerts: https://alerts.gitlab.net/#/alerts?filter=%7Btype%3D%22repository-mirroring%22%2C%20tier%3D%22sv%22%7D
- Label: gitlab-com/gl-infra/production~“Service::RepositoryMirroring”
Logging
Section titled “Logging”Troubleshooting Pointers
Section titled “Troubleshooting Pointers”- Mirror Updates Silently Failing
- Pull Mirror Overdue Queue is too Large
- Pull Mirroring Timeout with Large LFS Files
- Troubleshooting Repository Mirroring
Scalability
Section titled “Scalability”Sidekiq capacity is controlled by the mirror_max_capacity application setting. In response to mirroring lag or a need to process more mirroring jobs, this setting can be increased if the application has capacity.
This can be done through the Rails console:
ApplicationSetting.update_all(mirror_max_capacity: 2500)Or through the admin API.
Monitoring/Alerting
Section titled “Monitoring/Alerting”repository_update_mirror sidekiq worker dashboard
Contacting the team
Section titled “Contacting the team”Repository mirroring is owned by Create:Source Code Management.
Requests for help can be submitted using the source code group template.
Urgent, or less formal requests can be made directly on Slack in one of our team channels:
- #g_create_source_code (general)
- #g_create_source-code-review-fe (frontend)
- #g_create_source_code_be (backend)