diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-20 17:34:42 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-20 17:34:42 +0300 |
| commit | 9f46488805e86b1bc341ea1620b866016c2ce5ed (patch) | |
| tree | f9748c7e287041e37d6da49e0a29c9511dc34768 /doc/development/scalability.md | |
| parent | dfc92d081ea0332d69c8aca2f0e745cb48ae5e6d (diff) | |
Add latest changes from gitlab-org/gitlab@13-0-stable-ee
Diffstat (limited to 'doc/development/scalability.md')
| -rw-r--r-- | doc/development/scalability.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/scalability.md b/doc/development/scalability.md index 9607bce3bc4..ba25e169d66 100644 --- a/doc/development/scalability.md +++ b/doc/development/scalability.md @@ -214,7 +214,7 @@ Redis process. Single-core: Like PgBouncer, a single Redis process can only use one core. It does not support multi-threading. -Dumb secondaries: Redis secondaries (aka slaves) don't actually +Dumb secondaries: Redis secondaries (aka replicas) don't actually handle any load. Unlike PostgreSQL secondaries, they don't even serve read queries. They simply replicate data from the primary and take over only when the primary fails. @@ -231,8 +231,8 @@ election to determine a new leader. No leader: A Redis cluster can get into a mode where there are no primaries. For example, this can happen if Redis nodes are misconfigured to follow the wrong node. Sometimes this requires forcing one node to -become a primary via the [`SLAVEOF NO ONE` -command](https://redis.io/commands/slaveof). +become a primary via the [`REPLICAOF NO ONE` +command](https://redis.io/commands/replicaof). ### Sidekiq |