diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-21 09:08:25 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-21 09:08:25 +0300 |
| commit | 8f306a7dc503ae0fed4acebc528f2bc2030dad83 (patch) | |
| tree | 80e62141eab6ff86ea7a184565afb32a650217d9 /doc/development/redis.md | |
| parent | 76937b2add54d9ecfd1310847e244ac833d90e3b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/redis.md')
| -rw-r--r-- | doc/development/redis.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/redis.md b/doc/development/redis.md index a8b7b84bb65..ec3ad4fa678 100644 --- a/doc/development/redis.md +++ b/doc/development/redis.md @@ -34,7 +34,7 @@ invalidated by a name change, it is better to include a hook that will expire the entry, instead of relying on the key changing. We don't use [Redis Cluster](https://redis.io/topics/cluster-tutorial) at the -moment, but may wish to in the future: [#118820](https://gitlab.com/gitlab-org/gitlab/issues/118820). +moment, but may wish to in the future: [#118820](https://gitlab.com/gitlab-org/gitlab/-/issues/118820). This imposes an additional constraint on naming: where GitLab is performing operations that require several keys to be held on the same Redis server - for |