diff options
author | Gabriel Mazetto <gabriel@gitlab.com> | 2018-03-09 13:32:18 +0000 |
---|---|---|
committer | Nick Thomas <nick@gitlab.com> | 2018-03-09 13:32:18 +0000 |
commit | 9b5e4ecc55e85304c0eb3e9d3713edbc9bebbeab (patch) | |
tree | 4128cd28482de9646a26e8987d0af6c0a10865e6 /doc/administration/raketasks | |
parent | cd7fcfd5779716c302608ce462996809f952ceec (diff) | |
download | gitlab-ce-9b5e4ecc55e85304c0eb3e9d3713edbc9bebbeab.tar.gz |
Add rake task to cleanup any existing exclusive lease
Diffstat (limited to 'doc/administration/raketasks')
-rw-r--r-- | doc/administration/raketasks/maintenance.md | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/administration/raketasks/maintenance.md b/doc/administration/raketasks/maintenance.md index ecf92c379fd..2b4252a7b1d 100644 --- a/doc/administration/raketasks/maintenance.md +++ b/doc/administration/raketasks/maintenance.md @@ -240,3 +240,31 @@ sudo gitlab-rake gitlab:tcp_check[example.com,80] cd /home/git/gitlab sudo -u git -H bundle exec rake gitlab:tcp_check[example.com,80] RAILS_ENV=production ``` + +## Clear exclusive lease (DANGER) + +GitLab uses a shared lock mechanism: `ExclusiveLease` to prevent simultaneous operations +in a shared resource. An example is running periodic garbage collection on repositories. + +In very specific situations, a operation locked by an Exclusive Lease can fail without +releasing the lock. If you can't wait for it to expire, you can run this task to manually +clear it. + +To clear all exclusive leases: + +DANGER: **DANGER**: +Don't run it while GitLab or Sidekiq is running + +```bash +sudo gitlab-rake gitlab:exclusive_lease:clear +``` + +To specify a lease `type` or lease `type + id`, specify a scope: + +```bash +# to clear all leases for repository garbage collection: +sudo gitlab-rake gitlab:exclusive_lease:clear[project_housekeeping:*] + +# to clear a lease for repository garbage collection in a specific project: (id=4) +sudo gitlab-rake gitlab:exclusive_lease:clear[project_housekeeping:4] +``` |