diff options
| author | Douwe Maan <douwe@gitlab.com> | 2017-10-31 12:18:47 +0000 |
|---|---|---|
| committer | Douwe Maan <douwe@gitlab.com> | 2017-10-31 12:18:47 +0000 |
| commit | 682923b79b6e9631d6b0d4b9db096773e5b0c33a (patch) | |
| tree | eef59151d8b82b9eb3d673d5568eaeca3a492fe9 /doc/administration | |
| parent | de16fb138b1f0d9801c1a88cdabb4a3e3bdc6f5e (diff) | |
| parent | 9c41c7ac1ea2e9085424e3eb1fe9924243affb7c (diff) | |
| download | gitlab-ce-682923b79b6e9631d6b0d4b9db096773e5b0c33a.tar.gz | |
Merge branch '3674-hashed-storage-attachments' into 'master'
Hashed Storage support for Attachments
See merge request gitlab-org/gitlab-ce!15068
Diffstat (limited to 'doc/administration')
| -rw-r--r-- | doc/administration/repository_storage_types.md | 25 |
1 files changed, 24 insertions, 1 deletions
diff --git a/doc/administration/repository_storage_types.md b/doc/administration/repository_storage_types.md index fa882bbe28a..0cb2648cc1e 100644 --- a/doc/administration/repository_storage_types.md +++ b/doc/administration/repository_storage_types.md @@ -25,7 +25,10 @@ Any change in the URL will need to be reflected on disk (when groups / users or of load in big installations, and can be even worst if they are using any type of network based filesystem. Last, for GitLab Geo, this storage type means we have to synchronize the disk state, replicate renames in the correct -order or we may end-up with wrong repository or missing data temporarily. +order or we may end-up with wrong repository or missing data temporarily. + +This pattern also exists in other objects stored in GitLab, like issue Attachments, GitLab Pages artifacts, +Docker Containers for the integrated Registry, etc. ## Hashed Storage @@ -67,3 +70,23 @@ To migrate your existing projects to the new storage type, check the specific [r [ce-28283]: https://gitlab.com/gitlab-org/gitlab-ce/issues/28283 [rake tasks]: raketasks/storage.md#migrate-existing-projects-to-hashed-storage [storage-paths]: repository_storage_types.md + +### Hashed Storage coverage + +We are incrementally moving every storable object in GitLab to the Hashed Storage pattern. You can check the current +coverage status below. + +Not that things stored in S3 compatible endpoint, will not have the downsides mentioned earlier, if they are not +prefixed with `#{namespace}/#{project_name}`, which is true for CI Cache and LFS Objects. + +| Storable Object | Legacy Storage | Hashed Storage | S3 Compatible | GitLab Version | +| ----------------| -------------- | -------------- | ------------- | -------------- | +| Repository | Yes | Yes | - | 10.0 | +| Attachments | Yes | Yes | - | 10.2 | +| Avatars | Yes | No | - | - | +| Pages | Yes | No | - | - | +| Docker Registry | Yes | No | - | - | +| CI Build Logs | No | No | - | - | +| CI Artifacts | No | No | - | - | +| CI Cache | No | No | Yes | - | +| LFS Objects | Yes | No | Yes (EEP) | - | |