diff options
| author | Stan Hu <stanhu@gmail.com> | 2017-08-10 23:53:08 +0000 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2017-08-10 23:53:08 +0000 |
| commit | 18de34bd69d2f9897bba9d673e2e245417c018c3 (patch) | |
| tree | c6cff7e937e5ffec9d7d455a3513ea00cc605164 | |
| parent | 4ef10795ce5e24dc0f905daeb7236fe707a8c195 (diff) | |
| parent | 22995bdb3fdd9c882a224823411ee61015c2f071 (diff) | |
| download | gitlab-ce-18de34bd69d2f9897bba9d673e2e245417c018c3.tar.gz | |
Merge branch '36192-change-ha-docs-to-update-using-efs-as-nfs' into 'master'
Resolve "Change HA docs to update using EFS as NFS"
Closes #36192
See merge request !13400
| -rw-r--r-- | doc/administration/high_availability/nfs.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/administration/high_availability/nfs.md b/doc/administration/high_availability/nfs.md index 90a2e9298bf..e09ccaba08c 100644 --- a/doc/administration/high_availability/nfs.md +++ b/doc/administration/high_availability/nfs.md @@ -42,6 +42,10 @@ GitLab does not recommend using EFS with GitLab. are allocated. For smaller volumes, users may experience decent performance for a period of time due to 'Burst Credits'. Over a period of weeks to months credits may run out and performance will bottom out. +- To keep "Burst Credits" available, it may be necessary to provision more space + with 'dummy data'. However, this may get expensive. +- Another option to maintain "Burst Credits" is to use FS Cache on the server so + that AWS doesn't always have to go into EFS to access files. - For larger volumes, allocated IOPS may not be the problem. Workloads where 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. |