diff options
Diffstat (limited to 'doc/administration/redis/troubleshooting.md')
| -rw-r--r-- | doc/administration/redis/troubleshooting.md | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/administration/redis/troubleshooting.md b/doc/administration/redis/troubleshooting.md index 947db2c1d4e..5f0be709d78 100644 --- a/doc/administration/redis/troubleshooting.md +++ b/doc/administration/redis/troubleshooting.md @@ -88,11 +88,9 @@ You must make sure you are defining the same value in `redis['master_name']` and `redis['master_password']` as you defined for your sentinel node. The way the Redis connector `redis-rb` works with sentinel is a bit -non-intuitive. We try to hide the complexity in omnibus, but it still requires +non-intuitive. We try to hide the complexity in the Linux package, but it still requires a few extra configurations. ---- - To make sure your configuration is correct: 1. SSH into your GitLab application server @@ -135,7 +133,7 @@ To make sure your configuration is correct: You should see a different port after a few seconds delay (the failover/reconnect time). -## Troubleshooting a non-bundled Redis with an installation from source +## Troubleshooting a non-bundled Redis with a self-compiled installation If you get an error in GitLab like `Redis::CannotConnectError: No sentinels available.`, there may be something wrong with your configuration files or it can be related |