Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Jérome Perrin
gitlab-ce
Commits
9b5e4ecc
Commit
9b5e4ecc
authored
Mar 09, 2018
by
Gabriel Mazetto
Committed by
Nick Thomas
Mar 09, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add rake task to cleanup any existing exclusive lease
parent
cd7fcfd5
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
59 additions
and
0 deletions
+59
-0
doc/administration/raketasks/maintenance.md
doc/administration/raketasks/maintenance.md
+28
-0
lib/gitlab/exclusive_lease.rb
lib/gitlab/exclusive_lease.rb
+10
-0
lib/tasks/gitlab/exclusive_lease.rake
lib/tasks/gitlab/exclusive_lease.rake
+9
-0
spec/lib/gitlab/exclusive_lease_spec.rb
spec/lib/gitlab/exclusive_lease_spec.rb
+12
-0
No files found.
doc/administration/raketasks/maintenance.md
View file @
9b5e4ecc
...
...
@@ -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]
```
lib/gitlab/exclusive_lease.rb
View file @
9b5e4ecc
...
...
@@ -41,6 +41,16 @@ module Gitlab
"gitlab:exclusive_lease:
#{
key
}
"
end
# Removes any existing exclusive_lease from redis
# Don't run this in a live system without making sure no one is using the leases
def
self
.
reset_all!
(
scope
=
'*'
)
Gitlab
::
Redis
::
SharedState
.
with
do
|
redis
|
redis
.
scan_each
(
match:
redis_shared_state_key
(
scope
)).
each
do
|
key
|
redis
.
del
(
key
)
end
end
end
def
initialize
(
key
,
uuid:
nil
,
timeout
:)
@redis_shared_state_key
=
self
.
class
.
redis_shared_state_key
(
key
)
@timeout
=
timeout
...
...
lib/tasks/gitlab/exclusive_lease.rake
0 → 100644
View file @
9b5e4ecc
namespace
:gitlab
do
namespace
:exclusive_lease
do
desc
'GitLab | Clear existing exclusive leases for specified scope (default: *)'
task
:clear
,
[
:scope
]
=>
[
:environment
]
do
|
_
,
args
|
args
[
:scope
].
nil?
?
Gitlab
::
ExclusiveLease
.
reset_all!
:
Gitlab
::
ExclusiveLease
.
reset_all!
(
args
[
:scope
])
puts
'All exclusive lease entries were removed.'
end
end
end
spec/lib/gitlab/exclusive_lease_spec.rb
View file @
9b5e4ecc
...
...
@@ -88,4 +88,16 @@ describe Gitlab::ExclusiveLease, :clean_gitlab_redis_shared_state do
expect
(
lease
.
ttl
).
to
be_nil
end
end
describe
'.reset_all!'
do
it
'removes all existing lease keys from redis'
do
uuid
=
described_class
.
new
(
unique_key
,
timeout:
3600
).
try_obtain
expect
(
described_class
.
get_uuid
(
unique_key
)).
to
eq
(
uuid
)
described_class
.
reset_all!
expect
(
described_class
.
get_uuid
(
unique_key
)).
to
be_falsey
end
end
end
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment