diff options
Diffstat (limited to 'doc/administration/geo/setup/database.md')
| -rw-r--r-- | doc/administration/geo/setup/database.md | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/doc/administration/geo/setup/database.md b/doc/administration/geo/setup/database.md index 471bae72c5b..13615825a14 100644 --- a/doc/administration/geo/setup/database.md +++ b/doc/administration/geo/setup/database.md @@ -1,8 +1,7 @@ --- stage: Systems group: Geo -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments -type: howto +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments --- # Geo database replication **(PREMIUM SELF)** @@ -763,7 +762,7 @@ defaults default-server inter 3s fall 3 rise 2 on-marked-down shutdown-sessions frontend internal-postgresql-tcp-in - bind *:5000 + bind *:5432 mode tcp option tcplog @@ -900,6 +899,10 @@ For each node running a Patroni instance on the secondary site: gitlab_rails['auto_migrate'] = false ``` + When configuring `patroni['standby_cluster']['host']` and `patroni['standby_cluster']['port']`: + - `INTERNAL_LOAD_BALANCER_PRIMARY_IP` must point to the primary internal load balancer IP. + - `INTERNAL_LOAD_BALANCER_PRIMARY_PORT` must point to the frontend port [configured for the primary Patroni cluster leader](#step-2-configure-the-internal-load-balancer-on-the-primary-site). **Do not** use the PgBouncer frontend port. + 1. Reconfigure GitLab for the changes to take effect. This step is required to bootstrap PostgreSQL users and settings. @@ -952,8 +955,7 @@ If you want to run the Geo tracking database on a single node, see [Configure th A production-ready and secure setup for the tracking PostgreSQL DB requires at least three Consul nodes: two Patroni nodes, and one PgBouncer node on the secondary site. -Because of [issue 6587](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6587), Consul can't track multiple -services, so these must be different than the nodes used for the Standby Cluster database. +Consul can track multiple services, so you can choose to reuse the nodes used for the Standby Cluster database, though the instructions below do not show how to combine configurations when reusing Consul nodes. Be sure to use [password credentials](../../postgresql/replication_and_failover.md#database-authorization-for-patroni) and other database best practices. |