diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-12-20 16:37:47 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-12-20 16:37:47 +0300 |
commit | aee0a117a889461ce8ced6fcf73207fe017f1d99 (patch) | |
tree | 891d9ef189227a8445d83f35c1b0fc99573f4380 /doc/administration/redis | |
parent | 8d46af3258650d305f53b819eabf7ab18d22f59e (diff) |
Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42
Diffstat (limited to 'doc/administration/redis')
-rw-r--r-- | doc/administration/redis/troubleshooting.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/administration/redis/troubleshooting.md b/doc/administration/redis/troubleshooting.md index 6ab3d55e06a..f4aab9d7b7f 100644 --- a/doc/administration/redis/troubleshooting.md +++ b/doc/administration/redis/troubleshooting.md @@ -20,6 +20,18 @@ Before proceeding with the troubleshooting below, check your firewall rules: - Connect to other Sentinel machines via TCP in `26379` - Connect to the Redis machines via TCP in `6379` +## Basic Redis activity check + +Start Redis troubleshooting with a basic Redis activity check: + +1. Open a terminal on your GitLab server. +1. Run `gitlab-redis-cli --stat` and observe the output while it runs. +1. Go to your GitLab UI and browse to a handful of pages. Any page works, like + group or project overviews, issues, files in repositories, and so on. +1. Check the `stat` output again and verify that the values for `keys`, `clients`, + `requests`, and `connections` increases as you browse. If the numbers go up, + basic Redis functionality is working and GitLab can connect to it. + ## Troubleshooting Redis replication You can check if everything is correct by connecting to each server using |