Commit fb76dfe0 authored by Evan Read's avatar Evan Read

Merge branch 'docs-anchors4-ha' into 'master'

Docs: Fix anchors in HA docs

See merge request gitlab-org/gitlab-ce!25415
parents 4a5b3707 85f3a26d
...@@ -369,7 +369,7 @@ Now that the Redis servers are all set up, let's configure the Sentinel ...@@ -369,7 +369,7 @@ Now that the Redis servers are all set up, let's configure the Sentinel
servers. servers.
If you are not sure if your Redis servers are working and replicating If you are not sure if your Redis servers are working and replicating
correctly, please read the [Troubleshooting Replication](#troubleshooting-replication) correctly, please read the [Troubleshooting Replication](#troubleshooting-redis-replication)
and fix it before proceeding with Sentinel setup. and fix it before proceeding with Sentinel setup.
You must have at least `3` Redis Sentinel servers, and they need to You must have at least `3` Redis Sentinel servers, and they need to
......
...@@ -46,7 +46,7 @@ valuable information for the general setup. ...@@ -46,7 +46,7 @@ valuable information for the general setup.
Assuming that the Redis master instance IP is `10.0.0.1`: Assuming that the Redis master instance IP is `10.0.0.1`:
1. [Install Redis](../../install/installation.md#6-redis) 1. [Install Redis](../../install/installation.md#7-redis).
1. Edit `/etc/redis/redis.conf`: 1. Edit `/etc/redis/redis.conf`:
```conf ```conf
...@@ -72,7 +72,7 @@ Assuming that the Redis master instance IP is `10.0.0.1`: ...@@ -72,7 +72,7 @@ Assuming that the Redis master instance IP is `10.0.0.1`:
Assuming that the Redis slave instance IP is `10.0.0.2`: Assuming that the Redis slave instance IP is `10.0.0.2`:
1. [Install Redis](../../install/installation.md#6-redis) 1. [Install Redis](../../install/installation.md#7-redis).
1. Edit `/etc/redis/redis.conf`: 1. Edit `/etc/redis/redis.conf`:
```conf ```conf
......
...@@ -3,7 +3,7 @@ comments: false ...@@ -3,7 +3,7 @@ comments: false
--- ---
> **Note**: We **do not** recommend using the AWS Elastic File System (EFS), as it can result > **Note**: We **do not** recommend using the AWS Elastic File System (EFS), as it can result
in [significantly degraded performance](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/doc/administration/high_availability/nfs.md#aws-elastic-file-system). in [significantly degraded performance](../../../administration/high_availability/nfs.md#avoid-using-awss-elastic-file-system-efs).
# High Availability on AWS # High Availability on AWS
...@@ -182,7 +182,7 @@ Another option is to build a simple NFS server using a vanilla Linux server back ...@@ -182,7 +182,7 @@ Another option is to build a simple NFS server using a vanilla Linux server back
by AWS Elastic Block Storage (EBS). by AWS Elastic Block Storage (EBS).
> **Note:** GitLab does not recommend using AWS Elastic File System (EFS). See > **Note:** GitLab does not recommend using AWS Elastic File System (EFS). See
details in [High Availability NFS documentation](../../../administration/high_availability/nfs.md#aws-elastic-file-system) details in [High Availability NFS documentation](../../../administration/high_availability/nfs.md#avoid-using-awss-elastic-file-system-efs)
*** ***
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment