Resolve "Projects deleted on the primary may not be deleted on the secondary due to sidekiq losing jobs"
requested to merge 3651-projects-deleted-on-the-primary-may-not-be-deleted-on-the-secondary-due-to-sidekiq-losing-jobs into master
What does this MR do?
Destroy repositories synchronously when handling deleted events on Geo log cursor. It's important to notice that this will only perform a move operation synchronously which should not slow down the entire process, the repository removal still being performed asynchronously by GitlabShellWorker.
Why was this MR needed?
Repositories deleted on the primary may not be removed from the secondary due to Sidekiq losing jobs.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
What are the relevant issue numbers?
Closes #3651 (closed)