diff options
| author | Douglas Barbosa Alexandre <dbalexandre@gmail.com> | 2019-09-11 00:34:11 -0300 |
|---|---|---|
| committer | Douglas Barbosa Alexandre <dbalexandre@gmail.com> | 2019-09-11 11:51:29 -0300 |
| commit | b7b2207e013ee80d8849b5541eb7276e7793b275 (patch) | |
| tree | 3db85b16e16f886da1cee5e246122de0b6b563be | |
| parent | 43a40ac995f3a3e875497fa7a36ba546086a52fe (diff) | |
| download | gitlab-ce-da-geo-high-availability-docs.tar.gz | |
Update Geo HA docs to recommend Gitaly over NFSda-geo-high-availability-docs
| -rw-r--r-- | doc/administration/geo/replication/high_availability.md | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/doc/administration/geo/replication/high_availability.md b/doc/administration/geo/replication/high_availability.md index c737fa37077..a0684cfa726 100644 --- a/doc/administration/geo/replication/high_availability.md +++ b/doc/administration/geo/replication/high_availability.md @@ -88,16 +88,20 @@ major differences: Therefore, we will set up the HA components one-by-one, and include deviations from the normal HA setup. -### Step 1: Configure the Redis and NFS services on the **secondary** node +### Step 1: Configure the Redis and Gitaly services on the **secondary** node Configure the following services, again using the non-Geo high availability documentation: - [Configuring Redis for GitLab HA](../../high_availability/redis.md) for high availability. -- [NFS](../../high_availability/nfs.md) which will store data that is +- [Gitaly](../../high_availability/gitaly.md), which will store data that is synchronized from the **primary** node. +NOTE: **Note:** +[NFS](../../high_availability/nfs.md) can be used in place of Gitaly but is not +recommended. + ### Step 2: Configure the main read-only replica PostgreSQL database on the **secondary** node NOTE: **Note:** The following documentation assumes the database will be run on |