Commit 35d10237 authored by Evan Read's avatar Evan Read

Merge branch 'wc-gitaly-metadata-warn' into 'master'

Add explicit warning not to copy .gitaly-metadata

See merge request gitlab-org/gitlab!56365
parents 22a117e6 c22f7e2c
...@@ -136,6 +136,12 @@ To see if GitLab can access the repository file system directly, we use the foll ...@@ -136,6 +136,12 @@ To see if GitLab can access the repository file system directly, we use the foll
Direct Git access is enable by default in Omnibus GitLab because it fills in the correct repository Direct Git access is enable by default in Omnibus GitLab because it fills in the correct repository
paths in the GitLab configuration file `config/gitlab.yml`. This satisfies the UUID check. paths in the GitLab configuration file `config/gitlab.yml`. This satisfies the UUID check.
WARNING:
If directly copying repository data from a GitLab server to Gitaly, ensure that the metadata file,
default path `/var/opt/gitlab/git-data/repositories/.gitaly-metadata`, is not included in the transfer.
Copying this file causes GitLab to use the Rugged patches for repositories hosted on the Gitaly server,
leading to `Error creating pipeline` and `Commit not found` errors, or stale data.
### Transition to Gitaly Cluster ### Transition to Gitaly Cluster
For the sake of removing complexity, we must remove direct Git access in GitLab. However, we can't For the sake of removing complexity, we must remove direct Git access in GitLab. However, we can't
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment