Skip to content

GitLab Next

Project 'gitlab-com/infrastructure' was moved to 'gitlab-com/gl-infra/reliability'. Please update any links and bookmarks that may still have the old path.
Closed
Created by Nick Thomas@nick.thomas🔴10 of 11 tasks completed10/11 tasks

Sign-off on enabling hashed storage for GitLab.com

In %10.0 we introduced "hashed storage". When enabled, rather than storing projects on disk in a location determined by project.full_path, they are now stored in @hashed/aa/bb/full-hash. The hash is generated by SHAing the project ID.

This has several advantages, but chiefly it means that renaming projects no longer requires a racy mv command to be run on the project (and wiki) repository. This is particularly important for Geo setups, but large installations such as GitLab.com benefit in their own right.

I've been asked to evaluate the hashed storage system and attempt to determine whether %10.0 is a good time to enable it for GitLab.com and the Geo testbed.

There is also the question of migrating existing repositories to hashed storage. The migration path is still in development - see https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14067 - but I should evaluate that as well, as far as I'm able to.

Testing progress:

Edited by James Ramsay (ex-GitLab)