summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcia Ramos <virtua.creative@gmail.com>2018-10-29 11:12:58 +0000
committerMarcia Ramos <virtua.creative@gmail.com>2018-10-29 11:12:58 +0000
commitedb540c13cb0af299883e97d024fd796835acc4b (patch)
tree61ba0aebe5b0edbe9ea3eed731ffb4c324a77f2a
parent07b290f64dd9a5ee48186ff11cd9143cc488a817 (diff)
downloadgitlab-ce-lyle-master-patch-08152.tar.gz
Update headings for readability, SEO, and consistencylyle-master-patch-08152
-rw-r--r--doc/administration/high_availability/nfs.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/administration/high_availability/nfs.md b/doc/administration/high_availability/nfs.md
index 8329d783941..481eb692674 100644
--- a/doc/administration/high_availability/nfs.md
+++ b/doc/administration/high_availability/nfs.md
@@ -61,7 +61,7 @@ on an Linux NFS server, do the following:
2. Restart the NFS server process. For example, on CentOS run `service nfs restart`.
-## GitLab (and Git) don't work well with the AWS Elastic File System
+## Avoid using AWS's Elastic File System (EFS)
GitLab strongly recommends against using AWS Elastic File System (EFS).
Our support team will not be able to assist on performance issues related to
@@ -78,7 +78,7 @@ stored on a local volume.
For more details on another person's experience with EFS, see
[Amazon's Elastic File System: Burst Credits](https://rawkode.com/2017/04/16/amazons-elastic-file-system-burst-credits/)
-## PostgreSQL shouldn't use NFS
+## 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