@@ -80,25 +80,20 @@ by another folder with the next 2 characters. They are both stored in a special
...
@@ -80,25 +80,20 @@ by another folder with the next 2 characters. They are both stored in a special
### Hashed object pools
### Hashed object pools
CAUTION: **Beta:**
> [Introduced](https://gitlab.com/gitlab-org/gitaly/issues/1606) in GitLab 12.1.
Hashed objects pools are considered beta, and are not ready for production use.
Follow [gitaly#1548](https://gitlab.com/gitlab-org/gitaly/issues/1548) for
updates.
For deduplication of public forks and their parent repository, objects are pooled
Forks of public projects are deduplicated by creating a third repository, the object pool, containing the objects from the source project. Using `objects/info/alternates`, the source project and forks use the object pool for shared objects. Objects are moved from the source project to the object pool when housekeeping is run on the source project.
in an object pool. These object pools are a third repository where shared objects
are stored.
```ruby
```ruby
# object pool paths
# object pool paths
"@pools/#{hash[0..1]}/#{hash[2..3]}/#{hash}.git"
"@pools/#{hash[0..1]}/#{hash[2..3]}/#{hash}.git"
```
```
The object pool feature is behind the `object_pools` feature flag, and can be
Object pools can be disabled using the `object_pools` feature flag, and can be
enabled for individual projects by executing
disabled for individual projects by executing
`Feature.enable(:object_pools, Project.find(<id>))`. Note that the project has to