Skip to content
Snippets Groups Projects
Select Git revision
  • mshaw1-master-patch-68287
  • andr3-master-patch-06736
  • 363356-positive-intent-first
  • russell/improve-app-security-tools-introduction
  • 361217-delete-streaming-header
  • 361641-comments-discussion-header
  • morefice/add-drop-sequence-helper
  • remove-modal-ok-and-modal-cancel-slots-usage
  • sy-do-not-set-unsupported-sort-order-from-user-preference
  • master default protected
  • pedropombeiro/363308/add-html-field
  • qa-shl-group-inheritance-auth-spec
  • nd/bulk-update-member-await-active-state
  • fix-multiple-stop-actions-n-plus-1-queries
  • 358987-cleanup-feature-flag
  • release-tools/update-gitaly
  • migrate-retry-migration-button
  • id-jwt-gitlab-shell
  • 334810-add-placeholder-assignees-query
  • 363025-fix-epics-bulk-editing
  • v15.0.0-ee
  • v14.10.3-ee
  • v15.0.0-rc44-ee
  • v15.0.0-rc43-ee
  • v15.0.0-rc42-ee
  • v14.10.2-ee
  • v14.8.6-ee
  • v14.9.4-ee
  • v14.10.1-ee
  • v14.10.0-ee
  • v14.10.0-rc42-ee
  • v14.9.3-ee
  • v14.6.7-ee
  • v14.7.7-ee
  • v14.8.5-ee
  • v14.9.2-ee
  • v14.7.6-ee
  • v14.9.1-ee
  • v14.9.0-ee
  • v14.9.0-rc42-ee
40 results

repository_remove_remote_worker.rb

Forked from GitLab.org / GitLab
Source project has a limited visibility.
  • Patrick Steinhardt's avatar
    dea39b37
    workers: Remove support for asynchronous remote removal · dea39b37
    Patrick Steinhardt authored
    There are no users left of the worker which asynchronously removes
    a repository's on-disk remotes given that we only use in-memory remotes
    nowadays. While we can now remove the infrastructure to asynchronously
    remove remotes, we still need to retain the worker to make sure all jobs
    are drained on an upgrade. The worker's logic is stubbed out though to
    just do nothing: the worst that can happen with this is that we retain
    on-disk remotes in Gitaly storages, but Gitaly will eventually clean
    them up via repository maintenance anyway.
    dea39b37
    History
    workers: Remove support for asynchronous remote removal
    Patrick Steinhardt authored
    There are no users left of the worker which asynchronously removes
    a repository's on-disk remotes given that we only use in-memory remotes
    nowadays. While we can now remove the infrastructure to asynchronously
    remove remotes, we still need to retain the worker to make sure all jobs
    are drained on an upgrade. The worker's logic is stubbed out though to
    just do nothing: the worst that can happen with this is that we retain
    on-disk remotes in Gitaly storages, but Gitaly will eventually clean
    them up via repository maintenance anyway.