Geo: Backport Exclusive Lease to 9.2
What does this MR do?
Backports the ExclusiveLease changes from !1789 (merged)
Are there points in the code the reviewer needs to double check?
I've made the target branch 9-2-stable-ee
as this is a backport.
Why was this MR needed?
While we fixed this and refactored our SystemHook in !1789 (merged), because of the SystemHook refactor it did not land in time for 9.2. There are customers experiencing the issue right now, so I'm backporting the essential part of the first MR.
See #2512 (closed) for more information
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #2512 (closed)
Merge request reports
Activity
added 356 commits
-
3b328475...c3ffbf75 - 354 commits from branch
9-2-stable-ee
- d0815571 - Move GeoRepositoryFetchWorker logic to service class and use ExclusiveLease
- 9fdc2d66 - Codestyle changes
-
3b328475...c3ffbf75 - 354 commits from branch
changed milestone to %9.2
assigned to @brodock
assigned to @rspeicher
LGTM, thanks!
👍 Removing Pick into Stable since this goes directly into
9-2-stable-ee
. Heads-up @selfup @timothyandrew.mentioned in commit 853a377a