diff options
Diffstat (limited to 'doc/administration/nfs.md')
| -rw-r--r-- | doc/administration/nfs.md | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/administration/nfs.md b/doc/administration/nfs.md index 2a2e9f05312..a0170e6c4ef 100644 --- a/doc/administration/nfs.md +++ b/doc/administration/nfs.md @@ -20,31 +20,31 @@ file system performance, see ## Gitaly and NFS deprecation -Starting with GitLab version 14.0, support for NFS to store Git repository data will be deprecated. Technical customer support and engineering support will be available for the 14.x releases. Engineering will fix bugs and security vulnerabilities consistent with our [release and maintenance policy](../policy/maintenance.md#security-releases). +Starting with GitLab version 14.0, support for NFS to store Git repository data is deprecated. Technical customer support and engineering support is available for the 14.x releases. Engineering is fixing bugs and security vulnerabilities consistent with our [release and maintenance policy](../policy/maintenance.md#security-releases). -At the end of the 14.12 milestone (tenatively June 22nd, 2022) technical and engineering support for using NFS to store Git repository data will be officially at end-of-life. There will be no product changes or troubleshooting provided via Engineering, Security or Paid Support channels. +At the end of the 14.12 milestone (tentatively June 22nd, 2022) technical and engineering support for using NFS to store Git repository data will be officially at end-of-life. There will be no product changes or troubleshooting provided via Engineering, Security or Paid Support channels. For those customers still running earlier versions of GitLab, [our support eligibility and maintenance policy applies](https://about.gitlab.com/support/statement-of-support.html#version-support). -For the 14.x releases, we will continue to help with Git related tickets from customers running one or more Gitaly servers with its data stored on NFS. Examples may include: +For the 14.x releases, we continue to help with Git related tickets from customers running one or more Gitaly servers with its data stored on NFS. Examples may include: - Performance issues or timeouts accessing Git data - Commits or branches vanish - GitLab intermittently returns the wrong Git data (such as reporting that a repository has no branches) -Assistance will be limited to activities like: +Assistance is limited to activities like: - Verifying developers' workflow uses features like protected branches - Reviewing GitLab event data from the database to advise if it looks like a force push over-wrote branches - Verifying that NFS client mount options match our [documented recommendations](#mount-options) - Analyzing the GitLab Workhorse and Rails logs, and determining that `500` errors being seen in the environment are caused by slow responses from Gitaly -GitLab support will be unable to continue with the investigation if: +GitLab support is unable to continue with the investigation if: - The date of the request is on or after the release of GitLab version 15.0, and - Support Engineers and Management determine that all reasonable non-NFS root causes have been exhausted -If the issue is reproducible, or if it happens intermittently but regularly, GitLab Support will investigate providing the issue reproduces without the use of NFS. In order to reproduce without NFS, the affected repositories should be migrated to a different Gitaly shard, such as Gitaly cluster or a standalone Gitaly VM, backed with block storage. +If the issue is reproducible, or if it happens intermittently but regularly, GitLab Support can investigate providing the issue reproduces without the use of NFS. In order to reproduce without NFS, the affected repositories should be migrated to a different Gitaly shard, such as Gitaly cluster or a standalone Gitaly VM, backed with block storage. ### Why remove NFS for Git repository data @@ -438,7 +438,7 @@ the file system access GitLab requires. Workloads where many small files are wri a serialized manner, like `git`, are not well suited to cloud-based file systems. If you do choose to use these, avoid storing GitLab log files (for example, those in `/var/log/gitlab`) -there because this will also affect performance. We recommend that the log files be +there because this also affects performance. We recommend that the log files be stored on a local volume. For more details on the experience of using a cloud-based file systems with GitLab, @@ -447,12 +447,12 @@ see this [Commit Brooklyn 2019 video](https://youtu.be/K6OS8WodRBQ?t=313). ### Avoid using CephFS and GlusterFS GitLab strongly recommends against using CephFS and GlusterFS. -These distributed file systems are not well-suited for the GitLab input/output access patterns because Git uses many small files and access times and file locking times to propagate will make Git activity very slow. +These distributed file systems are not well-suited for the GitLab input/output access patterns because Git uses many small files and access times and file locking times to propagate makes Git activity very slow. ### Avoid using PostgreSQL with NFS GitLab strongly recommends against running your PostgreSQL database -across NFS. The GitLab support team will not be able to assist on performance issues related to +across NFS. The GitLab support team is not able to assist on performance issues related to this configuration. Additionally, this configuration is specifically warned against in the |