summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStan Hu <stanhu@gmail.com>2017-07-30 09:51:08 -0500
committerStan Hu <stanhu@gmail.com>2017-07-30 09:51:08 -0500
commit06a760e1392c540318058bd30ce644b20015caaf (patch)
tree6c5b16d5f106d4e36c559a8fbeb99dfd29ff6d00
parent02b25598cbedaaec96d8c9e52de7f969a5eb71a1 (diff)
downloadgitlab-ce-sh-aws-efs-docs.tar.gz
Add a note about EFS and GitLab log filessh-aws-efs-docs
[ci skip]
-rw-r--r--doc/administration/high_availability/nfs.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/administration/high_availability/nfs.md b/doc/administration/high_availability/nfs.md
index bd6b7327aed..90a2e9298bf 100644
--- a/doc/administration/high_availability/nfs.md
+++ b/doc/administration/high_availability/nfs.md
@@ -46,6 +46,10 @@ GitLab does not recommend using EFS with GitLab.
many small files are written in a serialized manner are not well-suited for EFS.
EBS with an NFS server on top will perform much better.
+In addition, avoid storing GitLab log files (e.g. those in `/var/log/gitlab`)
+because this will also affect performance. We recommend that the log files be
+stored on a local volume.
+
For more details on another person's experience with EFS, see
[Amazon's Elastic File System: Burst Credits](https://www.rawkode.io/2017/04/amazons-elastic-file-system-burst-credits/)