Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gitaly gitaly
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 561
    • Issues 561
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 56
    • Merge requests 56
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • gitalygitaly
  • Issues
  • #3033
Closed
Open
Issue created Aug 12, 2020 by Sami Hiltunen@samihiltunenMaintainer

Provide a migration tool for importing existing repositories in to generation tables

We should provide a tool that imports existing repositories that are not receiving writes in to the repositories tables so they can benefit from feature relying on this information, such as the read distribution.

Options:

  1. Walk the primary storage and create a record for each repository it has in the repositories and the storage_repositories. The automatic reconciler #2717 (closed) would then notice missing records for the secondaries and replicate to them. This should fix any inconsistencies due to dropped replication jobs. This will create a lot of replication jobs potentially but it guarantees the secondaries are brought consistent. However, this will include deleted repositories which did not have the operation properly replicated.

  2. Gather the information from the GitLab database. This would have the benefit of identifying repositories that should be deleted already.

I think we can go forward with option 1 and later filter out deleted repositories by cross referencing with the GitLab database if needed.

cc @zj-gitlab

Edited Aug 12, 2020 by Sami Hiltunen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking