Activating hashed storage
Since GitLab 12.0, hashed storage has become mandatory for using Geo. It was introduced in GitLab 10.0 and is much faster then the legacy storage option. The biggest use case for using hashed storage is that it eliminates the synchronization of URL and disk location(foldername). Before hashed storage, when a project was moved to another group, it was effectively relocated to another top-level folder. If, for any reason, a backup has to be restored, you had to hope that the name wasn't already taken. With hashed storage, every project uses a unique ID.
For Geo, this means that a move to another top-level folder will not trigger mass synchronizations. It only has to change a reference. This makes using hashed storage ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access