Skip to content
Snippets Groups Projects
Commit 05bb18a4 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis
Browse files

Merge branch 'rw-update-docs-rake-task-check-db-connections' into 'master'

Document gitlab:db:decomposition:connection_status rake task

See merge request https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/6781



Merged-by: default avatarAchilleas Pipinellis <axil@gitlab.com>
Approved-by: default avatarOmar Qunsul <oqunsul@gitlab.com>
Approved-by: default avatarAchilleas Pipinellis <axil@gitlab.com>
Approved-by: default avatarJason Plum <jplum@gitlab.com>
Reviewed-by: default avatarAchilleas Pipinellis <axil@gitlab.com>
Co-authored-by: default avatarRutger Wessels <rwessels@gitlab.com>
parents 9b7fe107 8f03f0de
No related branches found
No related tags found
No related merge requests found
Loading
Loading
@@ -675,10 +675,20 @@ this.
 
### Configuring multiple database connections
 
> The `gitlab:db:decomposition:connection_status` Rake task was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/111927) in GitLab 15.11.
In GitLab 16.0, GitLab will default to using two database connections, that point to the same
PostgreSQL database.
 
If you want to opt-in for this feature, you can update this setting in `/etc/gitlab/gitlab.rb`:
To opt-in for this feature, you first need to ensure PostgreSQL `max_connections` is high enough (using more than 50% of the available max connections).
You can verify this by running the following Rake task:
```shell
sudo gitlab-rake gitlab:db:decomposition:connection_status
```
If the task indicates that `max_connections` is high enough, you can enable this feature by updating
this setting in `/etc/gitlab/gitlab.rb`:
 
```ruby
gitlab_rails['databases']['ci']['enable'] = true
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment