Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedinexedi
  • gitlab-ce
  • Repository
  • gitlab-ce
  • lib
  • gitlab
  • git
  • object_pool.rb
Find file BlameHistoryPermalink
  • Zeger-Jan van de Weg's avatar
    Leave object pools when destroying projects · 752e9c18
    Zeger-Jan van de Weg authored Dec 17, 2018
    This action doesn't lean on reduplication, so a short call can me made
    to the Gitaly server to have the object pool remove its remote to the
    project pending deletion.
    https://gitlab.com/gitlab-org/gitaly/blob/f6cd55357/internal/git/objectpool/link.go#L58
    
    When an object pool doesn't have members, this would invalidate the need
    for a pool. So when a project leaves the pool, the pool will be
    destroyed on the background.
    
    Fixes: https://gitlab.com/gitlab-org/gitaly/issues/1415
    752e9c18
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7