Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
b4320ef6
Commit
b4320ef6
authored
Apr 23, 2021
by
Changzheng Liu
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update database_load_balancing.md
parent
33b50971
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/administration/database_load_balancing.md
doc/administration/database_load_balancing.md
+1
-1
No files found.
doc/administration/database_load_balancing.md
View file @
b4320ef6
...
...
@@ -39,7 +39,7 @@ at least 1 secondary in [hot standby](https://www.postgresql.org/docs/11/hot-sta
Load balancing also requires that the configured hosts
**always**
point to the
primary, even after a database failover. Furthermore, the additional hosts to
balance load among must
**always**
point to secondary databases. This means that
you should put a load balance in front of every database, and have GitLab connect
you should put a load balance
r
in front of every database, and have GitLab connect
to those load balancers.
For example, say you have a primary (
`db1.gitlab.com`
) and two secondaries,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment