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
97bcc758
Commit
97bcc758
authored
Oct 19, 2021
by
Craig Norris
Committed by
Marcel Amirault
Oct 19, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Revise Geo database replication intro
parent
6eff0eaa
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
14 deletions
+12
-14
doc/administration/geo/setup/database.md
doc/administration/geo/setup/database.md
+12
-14
No files found.
doc/administration/geo/setup/database.md
View file @
97bcc758
...
...
@@ -7,23 +7,21 @@ type: howto
# Geo database replication **(PREMIUM SELF)**
NOTE:
If your GitLab installation uses external (not managed by Omnibus) PostgreSQL
instances, the Omnibus roles are unable to perform all necessary
configuration steps. In this case,
[
follow the Geo with external PostgreSQL instances document instead
](
external_database.md
)
.
This document describes the minimal required steps to replicate your primary
GitLab database to a secondary node's database. You may have to change some
values, based on attributes including your database's setup and size.
NOTE:
The stages of the setup process must be completed in the documented order.
Before attempting the steps in this stage,
[
complete all prior stages
](
../setup/index.md#using-omnibus-gitlab
)
.
If your GitLab installation uses external (not managed by Omnibus GitLab)
PostgreSQL instances, the Omnibus roles cannot perform all necessary
configuration steps. In this case, use the
[
Geo with external PostgreSQL instances
](
external_database.md
)
process instead.
This document describes the minimal steps you have to take to replicate your
**primary**
GitLab database to a
**secondary**
node's database. You may have to
change some values, based on attributes including your database's setup and
size.
The stages of the setup process must be completed in the documented order.
Before you attempt the steps in this stage,
[
complete all prior stages
](
../setup/index.md#using-omnibus-gitlab
)
.
You are encouraged to first read through all the steps before executing them
in your testing/production environment
.
Be sure to read and review all of these steps before you execute them in your
testing or production environments
.
## Single instance database replication
...
...
@@ -214,7 +212,7 @@ There is an [issue where support is being discussed](https://gitlab.com/gitlab-o
## - Prevents automatic upgrade of Postgres since it requires downtime of
## streaming replication to Geo secondary sites
## - Enables standard single-node GitLab services like NGINX, Puma, Redis,
##
Sidekiq, etc
. If you are segregating services, then you will need to
##
or Sidekiq
. If you are segregating services, then you will need to
## explicitly disable unwanted services.
##
roles
([
'geo_primary_role'
])
...
...
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