stage | group | info |
---|---|---|
Systems |
Geo |
To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments |
The following Rake tasks are for Geo installations. See also troubleshooting Geo for additional Geo Rake tasks.
There are few tasks you can run to schedule a Git housekeeping to start at the next repository sync in a secondary node:
This is equivalent of running git repack -d
on a bare repository.
Omnibus Installation
sudo gitlab-rake geo:git:housekeeping:incremental_repack
Source Installation
sudo -u git -H bundle exec rake geo:git:housekeeping:incremental_repack RAILS_ENV=production
This is equivalent of running git repack -d -A --pack-kept-objects
on a
bare repository which optionally, writes a reachability bitmap index
when this is enabled in GitLab.
Omnibus Installation
sudo gitlab-rake geo:git:housekeeping:full_repack
Source Installation
sudo -u git -H bundle exec rake geo:git:housekeeping:full_repack RAILS_ENV=production
This is equivalent of running git gc
on a bare repository, optionally writing
a reachability bitmap index when this is enabled in GitLab.
Omnibus Installation
sudo gitlab-rake geo:git:housekeeping:gc
Source Installation
sudo -u git -H bundle exec rake geo:git:housekeeping:gc RAILS_ENV=production
Under certain conditions your project registry can contain obsolete records, you
can remove them using the Rake task geo:run_orphaned_project_registry_cleaner
:
Omnibus Installation
sudo gitlab-rake geo:run_orphaned_project_registry_cleaner
Source Installation
sudo -u git -H bundle exec rake geo:run_orphaned_project_registry_cleaner RAILS_ENV=production