Geo with external PostgreSQL instances (PREMIUM SELF)
This document is relevant if you are using a PostgreSQL instance that is not managed by the Linux package. This includes cloud-managed instances, or manually installed and configured PostgreSQL instances.
NOTE: We strongly recommend running instances installed using the Linux package as they are actively developed and tested. We aim to be compatible with most external (not managed by Omnibus) databases but we do not guarantee compatibility.
SSH into a Rails node on your primary site and login as root:
## ## Geo Primary role ## - configure dependent flags automatically to enable Geo ## roles ['geo_primary_role'] ## ## The unique identifier for the Geo site. See ## https://docs.gitlab.com/ee/administration/geo_sites.html#common-settings ## gitlab_rails['geo_node_name'] = '<site_name_here>'
Reconfigure the Rails node for the change to take effect:
Execute the command below on the Rails node to define the site as primary site:
This command uses your defined
Configure the external database to be replicated
To set up an external database, you can either:
- Set up streaming replication yourself (for example Amazon RDS, or bare metal not managed by the Linux package).
- Manually perform the configuration of your Linux package installations as follows.
Leverage your cloud provider's tools to replicate the primary database
Given you have a primary site set up on AWS EC2 that uses RDS. You can now just create a read-only replica in a different region and the replication process is managed by AWS. Make sure you've set Network ACL (Access Control List), Subnet, and Security Group according to your needs, so the secondary Rails nodes can access the database.
The following instructions detail how to create a read-only replica for common cloud providers:
- Amazon RDS - Creating a Read Replica
- Azure Database for PostgreSQL - Create and manage read replicas in Azure Database for PostgreSQL
- Google Cloud SQL - Creating read replicas
When your read-only replica is set up, you can skip to configure your secondary site
Manually configure the primary database for replication
configures the primary node's database to be replicated by making changes to
postgresql.conf. Make the following configuration changes
manually to your external database configuration and ensure that you restart PostgreSQL
afterwards for the changes to take effect:
## ## Geo Primary Role ## - pg_hba.conf ## host all all <trusted primary IP>/32 md5 host replication gitlab_replicator <trusted primary IP>/32 md5 host all all <trusted secondary IP>/32 md5 host replication gitlab_replicator <trusted secondary IP>/32 md5
## ## Geo Primary Role ## - postgresql.conf ## wal_level = hot_standby max_wal_senders = 10 wal_keep_segments = 50 max_replication_slots = 1 # number of secondary instances hot_standby = on
Manually configure the replica database
Make the following configuration changes manually to your
of your external replica database and ensure that you restart PostgreSQL afterwards
for the changes to take effect:
## ## Geo Secondary Role ## - pg_hba.conf ## host all all <trusted secondary IP>/32 md5 host replication gitlab_replicator <trusted secondary IP>/32 md5 host all all <trusted primary IP>/24 md5
## ## Geo Secondary Role ## - postgresql.conf ## wal_level = hot_standby max_wal_senders = 10 wal_keep_segments = 10 hot_standby = on
Configure secondary site to use the external read-replica
With Linux package installations, the
has three main functions:
- Configure the replica database.
- Configure the tracking database.
- Enable the Geo Log Cursor (not covered in this section).
To configure the connection to the external read-replica database and enable Log Cursor:
SSH into each Rails, Sidekiq and Geo Log Cursor node on your secondary site and login as root:
/etc/gitlab/gitlab.rband add the following
## ## Geo Secondary role ## - configure dependent flags automatically to enable Geo ## roles ['geo_secondary_role'] # note this is shared between both databases, # make sure you define the same password in both gitlab_rails['db_password'] = '<your_password_here>' gitlab_rails['db_username'] = 'gitlab' gitlab_rails['db_host'] = '<database_read_replica_host>' # Disable the bundled Omnibus PostgreSQL, since we are # using an external PostgreSQL postgresql['enable'] = false
Save the file and reconfigure GitLab
Configure the tracking database
Secondary sites use a separate PostgreSQL installation as a tracking
database to keep track of replication status and automatically recover from
potential replication issues. The Linux package automatically configures a tracking database
roles ['geo_secondary_role'] is set.
If you want to run this database external to your Linux package installation, use the following instructions.
Cloud-managed database services
If you are using a cloud-managed service for the tracking database, you may need
to grant additional roles to your tracking database user (by default, this is
- Amazon RDS requires the
- Azure Database for PostgreSQL requires the
- Google Cloud SQL requires the
This is for the installation of extensions during installation and upgrades. As an alternative, ensure the extensions are installed manually, and read about the problems that may arise during future GitLab upgrades.
NOTE: If you want to use Amazon RDS as a tracking database, make sure it has access to the secondary database. Unfortunately, just assigning the same security group is not enough as outbound rules do not apply to RDS PostgreSQL databases. Therefore, you need to explicitly add an inbound rule to the read-replica's security group allowing any TCP traffic from the tracking database on port 5432.
Create the tracking database
Create and configure the tracking database in your PostgreSQL instance:
Set up PostgreSQL according to the database requirements document.
Set up a
gitlab_geouser with a password of your choice, create the
gitlabhq_geo_productiondatabase, and make the user an owner of the database. You can see an example of this setup in the self-compiled installation documentation.
If you are not using a cloud-managed PostgreSQL database, ensure that your secondary site can communicate with your tracking database by manually changing the
pg_hba.confthat is associated with your tracking database. Remember to restart PostgreSQL afterwards for the changes to take effect:
## ## Geo Tracking Database Role ## - pg_hba.conf ## host all all <trusted tracking IP>/32 md5 host all all <trusted secondary IP>/32 md5
Configure GitLab to use this database. These steps are for Linux package and Docker deployments.
SSH into a GitLab secondary server and login as root:
/etc/gitlab/gitlab.rbwith the connection parameters and credentials for the machine with the PostgreSQL instance:
geo_secondary['db_username'] = 'gitlab_geo' geo_secondary['db_password'] = '<your_password_here>' geo_secondary['db_host'] = '<tracking_database_host>' geo_secondary['db_port'] = <tracking_database_port> # change to the correct port geo_postgresql['enable'] = false # don't use internal managed instance
Save the file and reconfigure GitLab
Set up the database schema
The reconfigure in the steps above for Linux package and Docker deployments should handle these steps automatically.
This task creates the database schema. It requires the database user to be a superuser.
sudo gitlab-rake db:create:geo
Applying Rails database migrations (schema and data updates) is also performed by reconfigure. If
geo_secondary['auto_migrate'] = falseis set, or the schema was created manually, this step will be required:
sudo gitlab-rake db:migrate:geo