summaryrefslogtreecommitdiff
path: root/doc/development/scalability.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-02-14 03:09:01 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-02-14 03:09:01 +0000
commitc60a1173018e93e6bf433f87cb726adc979d1c8a (patch)
tree5231ab640b6b4914e4aee123dd2030a005216303 /doc/development/scalability.md
parente144369009f3404072f7e0f969f7cded93195a01 (diff)
downloadgitlab-ce-c60a1173018e93e6bf433f87cb726adc979d1c8a.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/scalability.md')
-rw-r--r--doc/development/scalability.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/scalability.md b/doc/development/scalability.md
index 37ffdbdbfde..3a9f5387b11 100644
--- a/doc/development/scalability.md
+++ b/doc/development/scalability.md
@@ -178,7 +178,7 @@ talking to the primary can mitigate this.
In the second case, existing connections to the newly-demoted replica
may execute a write query, which would fail. During a failover, it may
-be advantegeous to shut down the PgBouncer talking to the primary to
+be advantageous to shut down the PgBouncer talking to the primary to
ensure no more traffic arrives for it. The alternative would be to make
the application aware of the failover event and terminate its
connections gracefully.