diff options
author | Marcel Amirault <ravlen@gmail.com> | 2019-05-05 15:21:25 +0000 |
---|---|---|
committer | Achilleas Pipinellis <axil@gitlab.com> | 2019-05-05 15:21:25 +0000 |
commit | f4a1dcbe2fc31eca55c11be90588465924019972 (patch) | |
tree | 0a8cb51ba7f55ebf2235f607ed94e4c8abf39f00 /doc/administration/repository_storage_types.md | |
parent | 9b06dffc719ff068ccb690d193e2bce17ef05fcc (diff) | |
download | gitlab-ce-f4a1dcbe2fc31eca55c11be90588465924019972.tar.gz |
Docs: Merge Misc EE doc/administration files and dirs to CE
Diffstat (limited to 'doc/administration/repository_storage_types.md')
-rw-r--r-- | doc/administration/repository_storage_types.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/administration/repository_storage_types.md b/doc/administration/repository_storage_types.md index 88bf55296b2..4db3cbb9958 100644 --- a/doc/administration/repository_storage_types.md +++ b/doc/administration/repository_storage_types.md @@ -47,15 +47,15 @@ Any change in the URL will need to be reflected on disk (when groups / users or projects are renamed). This can add a lot of load in big installations, especially if using any type of network based filesystem. -For GitLab Geo in particular: Geo does work with legacy storage, but in some +CAUTION: **Caution:** +For Geo in particular: Geo does work with legacy storage, but in some edge cases due to race conditions it can lead to errors when a project is renamed multiple times in short succession, or a project is deleted and recreated under the same name very quickly. We expect these race events to be rare, and we have not observed a race condition side-effect happening yet. - This pattern also exists in other objects stored in GitLab, like issue Attachments, GitLab Pages artifacts, Docker Containers for the integrated -Registry, etc. +Registry, etc. Hashed storage is a requirement for Geo. ## Hashed Storage |