Skip to content

G
gitlab-ce
Commit 0df327a6 authored by Michael Kozono's avatar Michael Kozono Committed by Achilleas Pipinellis
Browse files
Options

Geo: Remove usage of single node roles from the multi-node doc

parent 0e08959b
Hide whitespace changes
Inline Side-by-side
Showing with 105 additions and 226 deletions
doc/administration/geo/replication/multiple_servers.md
View file @ 0df327a6
...@@ -17,69 +17,59 @@ described, it is possible to adapt these instructions to your needs. ...@@ -17,69 +17,59 @@ described, it is possible to adapt these instructions to your needs.
_[diagram source - GitLab employees only](https://docs.google.com/drawings/d/1z0VlizKiLNXVVVaERFwgsIOuEgjcUqDTWPdQYsE7Z4c/edit)_ _[diagram source - GitLab employees only](https://docs.google.com/drawings/d/1z0VlizKiLNXVVVaERFwgsIOuEgjcUqDTWPdQYsE7Z4c/edit)_
The topology above assumes the **primary** and **secondary** Geo clusters The topology above assumes the **primary** and **secondary** Geo sites
are located in two separate locations, on their own virtual network are located in two separate locations, on their own virtual network
with private IP addresses. The network is configured such that all machines in with private IP addresses. The network is configured such that all machines in
one geographic location can communicate with each other using their private IP addresses. one geographic location can communicate with each other using their private IP addresses.
The IP addresses given are examples and may be different depending on the The IP addresses given are examples and may be different depending on the
network topology of your deployment. network topology of your deployment.
The only external way to access the two Geo deployments is by HTTPS at The only external way to access the two Geo sites is by HTTPS at
`gitlab.us.example.com` and `gitlab.eu.example.com` in the example above. `gitlab.us.example.com` and `gitlab.eu.example.com` in the example above.
NOTE: NOTE:
The **primary** and **secondary** Geo deployments must be able to communicate to each other over HTTPS. The **primary** and **secondary** Geo sites must be able to communicate to each other over HTTPS.
## Redis and PostgreSQL for multiple nodes ## Redis and PostgreSQL for multiple nodes
Geo supports:
- Redis and PostgreSQL on the **primary** node configured for multiple nodes.
- Redis on **secondary** nodes configured for multiple nodes.
NOTE:
Support for PostgreSQL on **secondary** nodes in multi-node configuration
[is planned](https://gitlab.com/groups/gitlab-org/-/epics/2536).
Because of the additional complexity involved in setting up this configuration Because of the additional complexity involved in setting up this configuration
for PostgreSQL and Redis, it is not covered by this Geo multi-node documentation. for PostgreSQL and Redis, it is not covered by this Geo multi-node documentation.
For more information on setting up a multi-node PostgreSQL cluster and Redis cluster using the Omnibus GitLab package, see: For more information on setting up a multi-node PostgreSQL cluster and Redis cluster using the Omnibus GitLab package, see:
- [PostgreSQL multi-node documentation](../../postgresql/replication_and_failover.md) - [Geo multi-node database replication](../setup/database.md#multi-node-database-replication)
- [Redis multi-node documentation](../../redis/replication_and_failover.md) - [Redis multi-node documentation](../../redis/replication_and_failover.md)
NOTE: NOTE:
It is possible to use cloud hosted services for PostgreSQL and Redis, but this is beyond the scope of this document. It is possible to use cloud hosted services for PostgreSQL and Redis, but this is beyond the scope of this document.
## Prerequisites: Two working GitLab multi-node clusters ## Prerequisites: Two independently working GitLab multi-node sites
One cluster serves as the **primary** node. Use the One GitLab site serves as the Geo **primary** site. Use the
[GitLab multi-node documentation](../../reference_architectures/index.md) to set this up. If [GitLab reference architectures documentation](../../reference_architectures/index.md)
to set this up. You can use different reference architecture sizes for each Geo site. If
you already have a working GitLab instance that is in-use, it can be used as a you already have a working GitLab instance that is in-use, it can be used as a
**primary**. **primary** site.
The second cluster serves as the **secondary** node. Again, use the The second GitLab site serves as the Geo **secondary** site. Again, use the
[GitLab multi-node documentation](../../reference_architectures/index.md) to set this up. [GitLab reference architectures documentation](../../reference_architectures/index.md) to set this up.
It's a good idea to log in and test it. However, be aware that its data is It's a good idea to log in and test it. However, be aware that its data is
wiped out as part of the process of replicating from the **primary** node. wiped out as part of the process of replicating from the **primary** site.
## Configure the GitLab cluster to be the **primary** node ## Configure a GitLab site to be the Geo **primary** site
The following steps enable a GitLab cluster to serve as the **primary** node. The following steps enable a GitLab site to serve as the Geo **primary** site.
### Step 1: Configure the **primary** frontend servers ### Step 1: Configure the **primary** frontend nodes
1. Edit `/etc/gitlab/gitlab.rb` and add the following: 1. Edit `/etc/gitlab/gitlab.rb` and add the following:
```ruby ```ruby
## ##
## Enable the Geo primary role ## The unique identifier for the Geo site. It's recommended to use a
## ## physical location as a name, for example "us-east", instead of
roles ['geo_primary_role'] ## "secondary" or "geo". It's case-sensitive, and most characters are
## allowed. It should be the same for all nodes in a Geo site.
##
## The unique identifier for the Geo node.
## ##
gitlab_rails['geo_node_name'] = '<node_name_here>' gitlab_rails['geo_node_name'] = '<node_name_here>'
...@@ -93,150 +83,58 @@ After making these changes, [reconfigure GitLab](../../restart_gitlab.md#omnibus ...@@ -93,150 +83,58 @@ After making these changes, [reconfigure GitLab](../../restart_gitlab.md#omnibus
NOTE: NOTE:
PostgreSQL and Redis should have already been disabled on the PostgreSQL and Redis should have already been disabled on the
application servers during normal GitLab multi-node setup. Connections application nodes during normal GitLab multi-node setup. Connections
from the application servers to services on the backend servers should from the application nodes to services on the backend nodes should
have also been configured. See multi-node configuration documentation for have also been configured. See multi-node configuration documentation for
[PostgreSQL](../../postgresql/replication_and_failover.md#configuring-the-application-nodes) [PostgreSQL](../../postgresql/replication_and_failover.md#configuring-the-application-nodes)
and [Redis](../../redis/replication_and_failover.md#example-configuration-for-the-gitlab-application). and [Redis](../../redis/replication_and_failover.md#example-configuration-for-the-gitlab-application).
### Step 2: Configure the **primary** database ## Configure the other GitLab site to be a Geo **secondary** site
1. Edit `/etc/gitlab/gitlab.rb` and add the following:
```ruby
##
## Configure the Geo primary role and the PostgreSQL role
##
roles ['geo_primary_role', 'postgres_role']
```
## Configure a **secondary** node A **secondary** site is similar to any other GitLab multi-node site, with three
A **secondary** cluster is similar to any other GitLab multi-node cluster, with two
major differences: major differences:
- The main PostgreSQL database is a read-only replica of the **primary** node's - The main PostgreSQL database is a read-only replica of the Geo **primary** site's
PostgreSQL database. PostgreSQL database.
- There is also a single PostgreSQL database for the **secondary** cluster, - There is an additional PostgreSQL database for each Geo **secondary** site,
called the "tracking database", which tracks the synchronization state of called the "Geo tracking database", which tracks the replication and verification
various resources. state of various resources.
- There is an additional GitLab service [`geo-logcursor`](../index.md#geo-log-cursor)
Therefore, we set up the multi-node components one by one and include deviations Therefore, we set up the multi-node components one by one and include deviations
from the normal multi-node setup. However, we highly recommend configuring a from the normal multi-node setup. However, we highly recommend configuring a
brand-new cluster first, as if it were not part of a Geo setup. This allows brand-new GitLab site first, as if it were not part of a Geo setup. This allows
verifying that it is a working cluster. And only then should it be modified verifying that it is a working GitLab site. And only then should it be modified
for use as a Geo **secondary**. This helps to separate Geo setup problems from for use as a Geo **secondary** site. This helps to separate Geo setup problems from
unrelated problems. unrelated multi-node configuration problems.
### Step 1: Configure the Redis and Gitaly services on the **secondary** node ### Step 1: Configure the Redis and Gitaly services on the Geo **secondary** site
Configure the following services, again using the non-Geo multi-node Configure the following services, again using the non-Geo multi-node
documentation: documentation:
- [Configuring Redis for GitLab](../../redis/replication_and_failover.md#example-configuration-for-the-gitlab-application) for multiple nodes. - [Configuring Redis for GitLab](../../redis/replication_and_failover.md#example-configuration-for-the-gitlab-application) for multiple nodes.
- [Gitaly](../../gitaly/index.md), which stores data that is - [Gitaly](../../gitaly/index.md), which stores data that is
synchronized from the **primary** node. synchronized from the Geo **primary** site.
NOTE: NOTE:
[NFS](../../nfs.md) can be used in place of Gitaly but is not [NFS](../../nfs.md) can be used in place of Gitaly but is not
recommended. recommended.
### Step 2: Configure the main read-only replica PostgreSQL database on the **secondary** node ### Step 2: Configure Postgres streaming replication
NOTE:
The following documentation assumes the database runs on
a single node only. Multi-node PostgreSQL on **secondary** nodes is
[not currently supported](https://gitlab.com/groups/gitlab-org/-/epics/2536).
Configure the [**secondary** database](../setup/database.md) as a read-only replica of
the **primary** database. Use the following as a guide.
1. Generate an MD5 hash of the desired password for the database user that the
GitLab application uses to access the read-replica database:
The username (`gitlab` by default) is incorporated into the hash.
```shell
gitlab-ctl pg-password-md5 gitlab
# Enter password: <your_password_here>
# Confirm password: <your_password_here>
# fca0b89a972d69f00eb3ec98a5838484
```
Use this hash to fill in `<md5_hash_of_your_password>` in the next step.
1. Edit `/etc/gitlab/gitlab.rb` in the replica database machine, and add the
following:
```ruby
##
## Configure the Geo secondary role and the PostgreSQL role
##
roles ['geo_secondary_role', 'postgres_role']
##
## The unique identifier for the Geo node.
## This should match the secondary's application node.
##
gitlab_rails['geo_node_name'] = '<node_name_here>'
##
## Secondary address
## - replace '<secondary_node_ip>' with the public or VPC address of your Geo secondary node
## - replace '<tracking_database_ip>' with the public or VPC address of your Geo tracking database node
##
postgresql['listen_address'] = '<secondary_node_ip>'
postgresql['md5_auth_cidr_addresses'] = ['<secondary_node_ip>/32', '<tracking_database_ip>/32']
##
## Database credentials password (defined previously in primary node)
## - replicate same values here as defined in primary node
##
postgresql['sql_user_password'] = '<md5_hash_of_your_password>'
gitlab_rails['db_password'] = '<your_password_here>'
##
## When running the Geo tracking database on a separate machine, disable it
## here and allow connections from the tracking database host. And ensure
## the tracking database IP is in postgresql['md5_auth_cidr_addresses'] above.
##
geo_postgresql['enable'] = false
##
## Disable all other services that aren't needed. We had to enable
## geo_secondary_role to cause some configuration changes to postgresql, but
## the role enables single-node services by default.
##
alertmanager['enable'] = false
consul['enable'] = false
geo_logcursor['enable'] = false
gitaly['enable'] = false
gitlab_exporter['enable'] = false
gitlab_workhorse['enable'] = false
nginx['enable'] = false
node_exporter['enable'] = false
pgbouncer_exporter['enable'] = false
prometheus['enable'] = false
redis['enable'] = false
redis_exporter['enable'] = false
patroni['enable'] = false
sidekiq['enable'] = false
sidekiq_cluster['enable'] = false
puma['enable'] = false
```
After making these changes, [reconfigure GitLab](../../restart_gitlab.md#omnibus-gitlab-reconfigure) so the changes take effect. Follow the [Geo database replication instructions](../setup/database.md).
If using an external PostgreSQL instance, refer also to If using an external PostgreSQL instance, refer also to
[Geo with external PostgreSQL instances](../setup/external_database.md). [Geo with external PostgreSQL instances](../setup/external_database.md).
### Step 3: Configure the tracking database on the **secondary** node ### Step 3: Configure the Geo tracking database on the Geo **secondary** site
NOTE: If you want to run the Geo tracking database in a multi-node PostgreSQL cluster,
This documentation assumes the tracking database runs on then follow [Configuring Patroni cluster for the tracking PostgreSQL database](../setup/database.md#configuring-patroni-cluster-for-the-tracking-postgresql-database).
only a single machine, rather than as a PostgreSQL cluster.
Configure the tracking database. If you want to run the Geo tracking database on a single node, then follow
the instructions below.
1. Generate an MD5 hash of the desired password for the database user that the 1. Generate an MD5 hash of the desired password for the database user that the
GitLab application uses to access the tracking database: GitLab application uses to access the tracking database:
...@@ -254,8 +152,8 @@ Configure the tracking database. ...@@ -254,8 +152,8 @@ Configure the tracking database.
Use this hash to fill in `<tracking_database_password_md5_hash>` in the next Use this hash to fill in `<tracking_database_password_md5_hash>` in the next
step. step.
1. Edit `/etc/gitlab/gitlab.rb` in the tracking database machine, and add the 1. On the machine where the Geo tracking database is intended to run, add the
following: following to `/etc/gitlab/gitlab.rb`:
```ruby ```ruby
## ##
...@@ -271,29 +169,8 @@ Configure the tracking database. ...@@ -271,29 +169,8 @@ Configure the tracking database.
geo_postgresql['md5_auth_cidr_addresses'] = ['<replica_database_ip>/32'] geo_postgresql['md5_auth_cidr_addresses'] = ['<replica_database_ip>/32']
gitlab_rails['db_host'] = '<replica_database_ip>' gitlab_rails['db_host'] = '<replica_database_ip>'
# Prevent reconfigure from attempting to run migrations on the replica DB # Prevent reconfigure from attempting to run migrations on the replica database
gitlab_rails['auto_migrate'] = false gitlab_rails['auto_migrate'] = false
##
## Ensure unnecessary services are disabled
##
alertmanager['enable'] = false
consul['enable'] = false
geo_logcursor['enable'] = false
gitaly['enable'] = false
gitlab_exporter['enable'] = false
gitlab_workhorse['enable'] = false
nginx['enable'] = false
node_exporter['enable'] = false
pgbouncer_exporter['enable'] = false
postgresql['enable'] = false
prometheus['enable'] = false
redis['enable'] = false
redis_exporter['enable'] = false
patroni['enable'] = false
sidekiq['enable'] = false
sidekiq_cluster['enable'] = false
puma['enable'] = false
``` ```
After making these changes, [reconfigure GitLab](../../restart_gitlab.md#omnibus-gitlab-reconfigure) so the changes take effect. After making these changes, [reconfigure GitLab](../../restart_gitlab.md#omnibus-gitlab-reconfigure) so the changes take effect.
...@@ -301,27 +178,42 @@ After making these changes, [reconfigure GitLab](../../restart_gitlab.md#omnibus ...@@ -301,27 +178,42 @@ After making these changes, [reconfigure GitLab](../../restart_gitlab.md#omnibus
If using an external PostgreSQL instance, refer also to If using an external PostgreSQL instance, refer also to
[Geo with external PostgreSQL instances](../setup/external_database.md). [Geo with external PostgreSQL instances](../setup/external_database.md).
### Step 4: Configure the frontend application servers on the **secondary** node ### Step 4: Configure the frontend application nodes on the Geo **secondary** site
In the architecture overview, there are two machines running the GitLab In the minimal [architecture diagram](#architecture-overview) above, there are two
application services. These services are enabled selectively in the machines running the GitLab application services. These services are enabled
configuration. selectively in the configuration.
Configure the GitLab Rails application servers following the relevant steps Configure the GitLab Rails application nodes following the relevant steps
outlined in the [reference architectures](../../reference_architectures/index.md), outlined in the [reference architectures](../../reference_architectures/index.md),
then make the following modifications: then make the following modifications:
1. Edit `/etc/gitlab/gitlab.rb` on each application server in the **secondary** 1. Edit `/etc/gitlab/gitlab.rb` on each application node in the Geo **secondary**
cluster, and add the following: site, and add the following:
```ruby ```ruby
## ##
## Enable the Geo secondary role ## Enable GitLab application services. The application_role enables many services.
## Alternatively, you can choose to enable or disable specific services on
## different nodes to aid in horizontal scaling and separation of concerns.
##
roles ['application_role']
## `application_role` already enables this. You only need this line if
## you selectively enable individual services that depend on Rails, like
## `puma`, `sidekiq`, `geo-logcursor`, etc.
gitlab_rails['enable'] = true
##
## Enable Geo Log Cursor service
## ##
roles ['geo_secondary_role', 'application_role'] geo_logcursor['enable'] = true
## ##
## The unique identifier for the Geo node. ## The unique identifier for the Geo site. It's recommended to use a
## physical location as a name, for example "eu-west", instead of
## "secondary" or "geo". It's case-sensitive, and most characters are
## allowed. It should be the same for all nodes in a Geo site.
## ##
gitlab_rails['geo_node_name'] = '<node_name_here>' gitlab_rails['geo_node_name'] = '<node_name_here>'
...@@ -331,12 +223,11 @@ then make the following modifications: ...@@ -331,12 +223,11 @@ then make the following modifications:
gitlab_rails['auto_migrate'] = false gitlab_rails['auto_migrate'] = false
## ##
## Configure the connection to the tracking DB. And disable application ## Configure the connection to the tracking database
## servers from running tracking databases.
## ##
geo_secondary['enable'] = true
geo_secondary['db_host'] = '<geo_tracking_db_host>' geo_secondary['db_host'] = '<geo_tracking_db_host>'
geo_secondary['db_password'] = '<geo_tracking_db_password>' geo_secondary['db_password'] = '<geo_tracking_db_password>'
geo_postgresql['enable'] = false
## ##
## Configure connection to the streaming replica database, if you haven't ## Configure connection to the streaming replica database, if you haven't
...@@ -353,7 +244,7 @@ then make the following modifications: ...@@ -353,7 +244,7 @@ then make the following modifications:
## ##
## If you are using custom users not managed by Omnibus, you need to specify ## If you are using custom users not managed by Omnibus, you need to specify
## UIDs and GIDs like below, and ensure they match between servers in a ## UIDs and GIDs like below, and ensure they match between nodes in a
## cluster to avoid permissions issues ## cluster to avoid permissions issues
## ##
user['uid'] = 9000 user['uid'] = 9000
...@@ -369,14 +260,17 @@ If you had set up PostgreSQL cluster using the omnibus package and had set ...@@ -369,14 +260,17 @@ If you had set up PostgreSQL cluster using the omnibus package and had set
`postgresql['sql_user_password'] = 'md5 digest of secret'`, keep in `postgresql['sql_user_password'] = 'md5 digest of secret'`, keep in
mind that `gitlab_rails['db_password']` and `geo_secondary['db_password']` mind that `gitlab_rails['db_password']` and `geo_secondary['db_password']`
contains the plaintext passwords. This is used to let the Rails contains the plaintext passwords. This is used to let the Rails
servers connect to the databases. nodes connect to the databases.
NOTE: NOTE:
Make sure that current node IP is listed in `postgresql['md5_auth_cidr_addresses']` setting of your remote database. Make sure that current node's IP is listed in
`postgresql['md5_auth_cidr_addresses']` setting of the read-replica database to
allow Rails on this node to connect to Postgres.
After making these changes [Reconfigure GitLab](../../restart_gitlab.md#omnibus-gitlab-reconfigure) so the changes take effect. After making these changes [Reconfigure GitLab](../../restart_gitlab.md#omnibus-gitlab-reconfigure) so the changes take effect.
On the secondary the following GitLab frontend services are enabled: In the [architecture overview](#architecture-overview) topology, the following GitLab
services are enabled on the "frontend" nodes:
- `geo-logcursor` - `geo-logcursor`
- `gitlab-pages` - `gitlab-pages`
...@@ -388,60 +282,41 @@ On the secondary the following GitLab frontend services are enabled: ...@@ -388,60 +282,41 @@ On the secondary the following GitLab frontend services are enabled:
- `sidekiq` - `sidekiq`
- `puma` - `puma`
Verify these services by running `sudo gitlab-ctl status` on the frontend Verify these services exist by running `sudo gitlab-ctl status` on the frontend
application servers. application nodes.
### Step 5: Set up the LoadBalancer for the **secondary** node ### Step 5: Set up the LoadBalancer for the Geo **secondary** site
In this topology, a load balancer is required at each geographic location to The minimal [architecture diagram](#architecture-overview) above shows a load
route traffic to the application servers. balancer at each geographic location to route traffic to the application nodes.
See [Load Balancer for GitLab with multiple nodes](../../load_balancer.md) for See [Load Balancer for GitLab with multiple nodes](../../load_balancer.md) for
more information. more information.
### Step 6: Configure the backend application servers on the **secondary** node ### Step 6: Configure the backend application nodes on the Geo **secondary** site
The minimal reference architecture diagram above shows all application services The minimal [architecture diagram](#architecture-overview) above shows all application services
running together on the same machines. However, for multiple nodes we running together on the same machines. However, for multiple nodes we
[strongly recommend running all services separately](../../reference_architectures/index.md). [strongly recommend running all services separately](../../reference_architectures/index.md).
For example, a Sidekiq server could be configured similarly to the frontend For example, a Sidekiq node could be configured similarly to the frontend
application servers above, with some changes to run only the `sidekiq` service: application nodes above, with some changes to run only the `sidekiq` service:
1. Edit `/etc/gitlab/gitlab.rb` on each Sidekiq server in the **secondary** 1. Edit `/etc/gitlab/gitlab.rb` on each Sidekiq node in the Geo **secondary**
cluster, and add the following: site, and add the following:
```ruby ```ruby
##
## Enable the Geo secondary role
##
roles ['geo_secondary_role']
## ##
## Enable the Sidekiq service ## Enable the Sidekiq service
## ##
sidekiq['enable'] = true sidekiq['enable'] = true
gitlab_rails['enable'] = true
## ##
## Ensure unnecessary services are disabled ## The unique identifier for the Geo site. It's recommended to use a
## ## physical location as a name, for example "eu-west", instead of
alertmanager['enable'] = false ## "secondary" or "geo". It's case-sensitive, and most characters are
consul['enable'] = false ## allowed. It should be the same for all nodes in a Geo site.
gitaly['enable'] = false
gitlab_exporter['enable'] = false
gitlab_workhorse['enable'] = false
nginx['enable'] = false
node_exporter['enable'] = false
pgbouncer_exporter['enable'] = false
postgresql['enable'] = false
prometheus['enable'] = false
redis['enable'] = false
redis_exporter['enable'] = false
patroni['enable'] = false
puma['enable'] = false
##
## The unique identifier for the Geo node.
## ##
gitlab_rails['geo_node_name'] = '<node_name_here>' gitlab_rails['geo_node_name'] = '<node_name_here>'
...@@ -451,12 +326,11 @@ application servers above, with some changes to run only the `sidekiq` service: ...@@ -451,12 +326,11 @@ application servers above, with some changes to run only the `sidekiq` service:
gitlab_rails['auto_migrate'] = false gitlab_rails['auto_migrate'] = false
## ##
## Configure the connection to the tracking DB. And disable application ## Configure the connection to the tracking database
## servers from running tracking databases.
## ##
geo_secondary['enable'] = true
geo_secondary['db_host'] = '<geo_tracking_db_host>' geo_secondary['db_host'] = '<geo_tracking_db_host>'
geo_secondary['db_password'] = '<geo_tracking_db_password>' geo_secondary['db_password'] = '<geo_tracking_db_password>'
geo_postgresql['enable'] = false
## ##
## Configure connection to the streaming replica database, if you haven't ## Configure connection to the streaming replica database, if you haven't
...@@ -473,7 +347,7 @@ application servers above, with some changes to run only the `sidekiq` service: ...@@ -473,7 +347,7 @@ application servers above, with some changes to run only the `sidekiq` service:
## ##
## If you are using custom users not managed by Omnibus, you need to specify ## If you are using custom users not managed by Omnibus, you need to specify
## UIDs and GIDs like below, and ensure they match between servers in a ## UIDs and GIDs like below, and ensure they match between nodes in a
## cluster to avoid permissions issues ## cluster to avoid permissions issues
## ##
user['uid'] = 9000 user['uid'] = 9000
...@@ -484,8 +358,8 @@ application servers above, with some changes to run only the `sidekiq` service: ...@@ -484,8 +358,8 @@ application servers above, with some changes to run only the `sidekiq` service:
registry['gid'] = 9002 registry['gid'] = 9002
``` ```
You can similarly configure a server to run only the `geo-logcursor` service You can similarly configure a node to run only the `geo-logcursor` service
with `geo_logcursor['enable'] = true` and disabling Sidekiq with with `geo_logcursor['enable'] = true` and disabling Sidekiq with
`sidekiq['enable'] = false`. `sidekiq['enable'] = false`.
These servers do not need to be attached to the load balancer. These nodes do not need to be attached to the load balancer.
doc/administration/geo/setup/database.md
View file @ 0df327a6
...@@ -207,7 +207,12 @@ There is an [issue where support is being discussed](https://gitlab.com/gitlab-o ...@@ -207,7 +207,12 @@ There is an [issue where support is being discussed](https://gitlab.com/gitlab-o
```ruby ```ruby
## ##
## Geo Primary role ## Geo Primary role
## - configure dependent flags automatically to enable Geo ## - Configures Postgres settings for replication
## - 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
## explicitly disable unwanted services.
## ##
roles(['geo_primary_role']) roles(['geo_primary_role'])
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7